4-Deploy-motorVMC.md

@@ -83,7 +83,11 @@ The error was much more helpful in step 2.4 because [xxx's CONFIG file prints th
 <details>
 <summary>hint</summary>
 
-The **motorVMC/README.md** file indicates: *"The definitions of `MOTOR` and `EPICS_BASE` need to be corrected in `motorVMC/configure/RELEASE` before motorVMC can be built."*
+The **motorVMC/README.md** file indicates: 
+
+```
+The definitions of `MOTOR` and `EPICS_BASE` need to be corrected in `motorVMC/configure/RELEASE` before motorVMC can be built.
+```
 
 The **motorVMC/configure/RELEASE** file doesn't contain any definitions, but it does include other files **if they exist**.
 

5-Add-virtual-motors.md

@@ -42,6 +42,13 @@ index e7aba0e..39736e4 100644
 ```
 </details>
 
+
+<details>
+<summary>what does this mean?</summary>
+
+This step tells the build system **where** to find the **motorVMC** module, but it does not tell the build system **what** to include in the IOC build. This is determined by the **xxxApp/src/Makefile**.  
+</details>
+
 ### 5.2 Add motorVMC to the IOC's src/Makefile
 
 Add the motorVMC database and library to **xxxApp/src/Makefile**
@@ -119,7 +126,7 @@ endif
   - `$(PROD_NAME)_LIBS := vmc $($(PROD_NAME)_LIBS)`: 
     - This expression assigns the value `vmc` as the first element in the `$(PROD_NAME)_LIBS` variable, and it appends the existing value of `$(PROD_NAME)_LIBS` after `vmc`.
     - `$(PROD_NAME)_LIBS` is a variable that holds the names of libraries the IOC application depends on.
-    - Note: the `gcc -l` [flag](https://stackoverflow.com/questions/6231206/lib-prefix-on-libraries) requires libraries to omit the `lib` prefix and the `.a` extension. 
+    - Note: the convention is to omit the `lib` prefix and the `.a` extension (this is requirement from the `gcc -l` [flag](https://stackoverflow.com/questions/6231206/lib-prefix-on-libraries)). 
 
 </details>