From 698ade928bfb6b69f9ac25eadf05e441f4085ec2 Mon Sep 17 00:00:00 2001 From: Diogo21Costa Date: Tue, 19 Sep 2023 10:19:09 +0100 Subject: [PATCH] fix(doc): improve documentation readability Signed-off-by: Diogo21Costa --- source/bao_hyp/config.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/bao_hyp/config.rst b/source/bao_hyp/config.rst index 4a1211e..00e5101 100644 --- a/source/bao_hyp/config.rst +++ b/source/bao_hyp/config.rst @@ -68,7 +68,7 @@ Building Bao Hypervisor ----------------------- The configuration files for the Bao hypervisor are stored in a designated folder known as the configuration repository - ``CONFIG_REPO``. By default, -the ``CONFIG_REPO`` is set to the configs folder located in the top-level +the ``CONFIG_REPO`` is set to the ``configs`` folder located in the top-level directory of the Bao hypervisor. However, users have the flexibility to specify a different folder by using the ``CONFIG_REPO`` option in the make command during the hypervisor building process. For instance, the build command of Bao @@ -84,12 +84,12 @@ follows the nomenclature presented below: Considering a configuration named ``config-name``, the configuration naming can be provided in two formats: -**1. Single C Source File**: Save the configuration as a C source file with the\ -name ``config-name.c``. +**1. Single C Source File**: Save the configuration as a C source file with \ +the name ``config-name.c``. -**2. Directory Format:**: Alternatively, you can organize it as a directory\ +**2. Directory Format:**: Alternatively, you can organize it as a directory \ named ``config-name`` and place the C source file within, naming it\ -``config.c``. +``config.c``. In both cases, the build system will search for the configuration in the specified ``CONFIG_REPO`` using the defined naming convention. This allows