XDS app source: Minor edits for "flounder"

Amended commit to explain how CMake app-templates are used for
Flounder and how they are provided as a Git sub-module.

Amended commit to eliminate some whitespace.

Amended commit to get rid of note bullet saying you cannot
develop CMake applications in flounder.

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Change-Id: Ia3d0487d2d761d19ebe06388e5a315db9a7b8e53
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>

1 files changed, 25 insertions, 25 deletions

diff --git a/docs/part-1/create-app-get-source-files.md b/docs/part-1/create-app-get-source-files.md
index 7fca382..21e20d9 100755
--- a/docs/part-1/create-app-get-source-files.md
+++ b/docs/part-1/create-app-get-source-files.md
@@ -23,20 +23,20 @@ Two methods exist:
   Path mapping uses a volume shared between your development host and the server
   that is running XDS.
   The directory shared is `$HOME/xds-workspace`.
- 
+
   <!-- section-note -->
-  **NOTE:**
-
-  The path mapping method of sharing files is more efficient than
-  replicating the project on the XDS server.
-  However, you must clone the project under a directory that can be shared.
-  The most convenient directory is the default shared directory, which is
-  `$HOME/xds-workspace`.
-  
-  You could create additional shared volumes.
-  To create more shared volumes, See the
-  "[Create and Start a New Container](server-part.html#create-and-start-a-new-container)"
-  section.
+  **NOTES:**
+
+  - The path mapping method of sharing files is more efficient than
+    replicating the project on the XDS server.
+    However, you must clone the project under a directory that can be shared.
+    The most convenient directory is the default shared directory, which is
+    `$HOME/xds-workspace`.
+
+  - You could create additional shared volumes.
+    To create more shared volumes, See the
+    "[Create and Start a New Container](server-part.html#create-and-start-a-new-container)"
+    section.
 
 ## Which File Sharing Method Should I Choose?
 
@@ -53,18 +53,18 @@ Client Part configuration (i.e. Standalone, On-Premise or SaaS).
   file sharing.
 
 <!-- section-note -->
-**NOTE:**
-
-The
-[helloworld-native-application](https://github.com/iotbzh/helloworld-native-application)
-project is an AGL project that is based on CMake
-(i.e. [cmake-apps-module](https://git.automotivelinux.org/src/cmake-apps-module/)).
-For information on installing and using the CMake templates, see the
-"[Installing the CMake Templates](../../../../devguides/reference/cmakeafbtemplates/dev_guide/installing-cmake.html)"
-section.
-CMake templates, when used to develop applications
-with the AGL Application Framework, automatically generate Makefile rules
-(e.g. `remote-target-populate`) or scripts (e.g. `build/target/xxx` scripts).
+**NOTES:**
+
+- The
+  [helloworld-native-application](https://github.com/iotbzh/helloworld-native-application)
+  project is an AGL project that is based on CMake.
+
+- For the Flounder release, the AGL CMake template files are included
+  as a Git submodule (i.e.
+  [cmake-apps-module](https://git.automotivelinux.org/src/cmake-apps-module/)).
+
+- For information about CMake template files (app-template), please refer to the
+  "[App-templates](../../2_4-Use-app-templates/README.html)" topic.
 <!-- end-section-note -->
 
 ## Clone project