Cleanup: Fix incorrect statement in documentation.

The statement of "This is different from code:"build_sources_object"" for the build_sources_object documentation makes no sense.
Remove that part of the statement.
There are no functional changes to the specification, so the version date is unchanged.

diff --git a/level_3/fake/documents/settings.txt b/level_3/fake/documents/settings.txt
index 4a7b43df5064e1463a7ed65e03511f5c07dbb2a1..4ec88bc02df35b36ab5e0a0d1367fcf123c5c387 100644 (file)
--- a/level_3/fake/documents/settings.txt
+++ b/level_3/fake/documents/settings.txt
@@ -300,7 +300,7 @@ Settings Documentation:
     The built objects do not get linked and therefore no linker arguments apply.
     The built object files are named using the same name as the file with the file extension changed to the code:".o" extension.
     May include a relative sub-path to each individual source file (such as: code:"level_0/a.c level_0/b.c").
-    This is different from code:"build_sources_object" in that multiple files are supported and multiple object files are created.
+    Multiple files are supported and multiple object files are created.
 
   - code:"build_sources_object_shared"\:
     A collection of source files used for generating an object file with the same name as each source file.
@@ -308,7 +308,7 @@ Settings Documentation:
     The built objects do not get linked and therefore no linker arguments apply.
     The built object files are named using the same name as the file with the file extension changed to the code:".o" extension.
     May include a relative sub-path to each individual source file (such as: code:"level_0/a.c level_0/b.c").
-    This is different from code:"build_sources_object" in that multiple files are supported and multiple object files are created.
+    Multiple files are supported and multiple object files are created.
     These are applied to only shared builds.
 
   - code:"build_sources_object_static"\:
@@ -317,7 +317,7 @@ Settings Documentation:
     The built objects do not get linked and therefore no linker arguments apply.
     The built object files are named using the same name as the file with the file extension changed to the code:".o" extension.
     May include a relative sub-path to each individual source file (such as: code:"level_0/a.c level_0/b.c").
-    This is different from code:"build_sources_object" in that multiple files are supported and multiple object files are created.
+    Multiple files are supported and multiple object files are created.
     These are applied to only static builds.
 
   - code:"build_sources_program"\: