Update avenger-96-board.rst

documentation/source/quick-start/avenger-96-board.rst

@@ -87,19 +87,20 @@ Steps for building a BSP for ST's development boards is referred here: `<https:/
 
 Building the BSP for the Avenger96 follows the scheme of the above build process but starts with a different 'repo' manifest file:
 
-.. code-block:: console
+* Create the build directory following ST's recommendations at https://wiki.st.com/stm32mpu/wiki/Example_of_directory_structure_for_Packages.
 
-   - Create the build directory following ST's recommendations at https://wiki.st.com/stm32mpu/wiki/Example_of_directory_structure_for_Packages
 		
-   - Enter the working directory and execute the following commands
+* Enter the working directory and execute the following commands:
 	
-      $ repo init -u https://github.com/dh-electronics/manifest-av96 -b dunfell
+.. code-block:: console
+
+   $ repo init -u https://github.com/dh-electronics/manifest-av96 -b dunfell
 	  
-      $ repo sync
+   $ repo sync
 	  
-      $ source layers/meta-arrow/scripts/init-build-env.sh
+   $ source layers/meta-arrow/scripts/init-build-env.sh
 	  
-      $ bitbake av96-weston
+   $ bitbake av96-weston
 
 The last command will build the BSP. The full build will take about 1-2 hours dpending on machine and internet speed and will require around 25GB disk space. 
 
@@ -112,8 +113,8 @@ When the build completes it puts all the required files into the'deploy' folder.
 
    $ cd tmp-glibc/deploy/images/stm32mp1-av96/
      
-	$ ./scripts/create_sdcard_from_flashlayout.sh flashlayout_av96-weston/trusted/
-   FlashLayout_sdcard_stm32mp157a-av96-trusted.tsv
+	$ ./scripts/create_sdcard_from_flashlayout.sh flashlayout_av96-weston/trusted/ 
+      FlashLayout_sdcard_stm32mp157a-av96-trusted.tsv
 
 The last command creates FlashLayout_sdcard_stm32mp157a-av96-trusted.raw.
 We can write it to a uSD card with:
@@ -124,6 +125,7 @@ We can write it to a uSD card with:
 
 Once you have built your own AV96 Yocto image, your build provides all the files you need to use the Cube Programmer.
 
+
 Debugging
 *********
 You can debug an application using OpenOCD and GDB. The Solution proposed below is based on the Linux STM32MP1 SDK OpenOCD and is available only for a Linux environment. The firmware must first be loaded by the Cortex®-A7. Developer then attaches the debugger to the running Zephyr using OpenOCD.