Processed review comments on Core Build System description.

doc/org.eclipse.cdt.doc.user/src/asciidoc/core_build_system.adoc

@@ -21,7 +21,8 @@ endif::[]
 
 = Core Build System
 
-The Core Build System is the successor of the Managed Build System.
+The Core Build System is the successor of the legacy Managed Build
+System.
 
 The classical Makefile projects are based on the Managed Build System.
 Managed Build projects can generate a Makefile based on GUI controlled
@@ -35,7 +36,7 @@ Makefile projects. The CDT LaunchBar plays a central role and is used
 for building and launching the program. The philosophy is "Build for
 launch". It simplified the flow a lot.
 
-These are the main differences with the old Managed Build System:
+These are the main differences with the Managed Build System:
 
 * No build configurations. No build file (Makefile or
   CMakeLists.txt) generation. The user writes it by hand. A
@@ -49,8 +50,16 @@ These are the main differences with the old Managed Build System:
   needed for indexing, are extracted from the build step. For CMake
   projects this is done via the generated JSON file. For Makefile
   projects it is extracted from the build step console output.
-* Using existing code is simply done by creating a new project on top
-  of the existing code. No more project import.
+* Simpler wizards. Creating a CMake project is a simple one page
+  wizard. Using existing code is simply done by creating a new project
+  on top of the existing code. No more project import
+  (menu:File[Import...]).
+
+Core Build connects CDT projects to industry standard external build
+systems like CMake, Makefile, and Meson. The removal of the CDT
+specific build configurations makes that Core Build projects can
+easily be shared with other IDEs, command-line use, and Continuous
+Integration (CI) flows.
 
 Thanks to the auto discovery the indexing of the C/C++ code has
 improved, because all compilation flags are known per file. Especially