瀏覽代碼

README small tweak

Robin Mueller 4 年之前
父節點
當前提交
1a2ac70964
共有 1 個文件被更改,包括 4 次插入3 次删除
  1. 4 3
      README.md

+ 4 - 3
README.md

@@ -37,7 +37,8 @@ It will compile a project for the `F4` family by default, but you can also compi
 # Usage
 # Usage
 
 
 First of all you need to configure toolchain and library paths using CMake variables. There are
 First of all you need to configure toolchain and library paths using CMake variables. There are
-generally three ways to do this
+generally three ways to do this:
+
 1. Pass the variables through command line during cmake run with passed to CMake with 
 1. Pass the variables through command line during cmake run with passed to CMake with 
    `-D<VAR_NAME>=...`
    `-D<VAR_NAME>=...`
 2. Set the variables inside your `CMakeLists.txt`
 2. Set the variables inside your `CMakeLists.txt`
@@ -62,7 +63,7 @@ These configuration variables are optional:
 ### Helper script on Unix shells
 ### Helper script on Unix shells
 
 
 If you have access to a Unix shell, which is the default terminal on Linux, or tools like
 If you have access to a Unix shell, which is the default terminal on Linux, or tools like
-`MinGW64` or `git bash` on Windows, you can write a small `path_helper.sh` script like this
+`MinGW64` or `git bash` on Windows, you can write a small `path_helper.sh` script like this:
 
 
 ```sh
 ```sh
 export STM32_TOOLCHAIN_PATH="<ToolchainPath>"
 export STM32_TOOLCHAIN_PATH="<ToolchainPath>"
@@ -74,7 +75,7 @@ and then use `. path_helper.sh` to set up the environment for the local terminal
 
 
 ### Helper script in Powershell
 ### Helper script in Powershell
 
 
-On Windows, you can use a Powershell script `path_helper.ps1`to set up the environment
+On Windows, you can use a Powershell script `path_helper.ps1`to set up the environment:
 
 
 ```sh
 ```sh
 $env:STM32_TOOLCHAIN_PATH = "<ToolchainPath>"
 $env:STM32_TOOLCHAIN_PATH = "<ToolchainPath>"