[sdk/kdesrc-build/docbook_historied_per_file] doc: doc: it's the software that's being built

[Luigi Toscano]

Git commit 54abdc70cdedf92d3b9b661f012e24c6fee2f412 by Luigi Toscano.
Committed on 04/07/2018 at 22:30.
Pushed by ashark into branch 'docbook_historied_per_file'.

doc: it's the software that's being built

Most of the time the sentences revolve around any software by KDE.
In one case the sentence is about Plasma specifically.

Original commit: 15669c64
https://invent.kde.org/sdk/kdesrc-build/-/commit/15669c6499756235f576db62a951157b79f6375c

M  +1    -1    doc/features/features-overview.docbook
M  +1    -1    doc/getting-started/before-building.docbook
M  +4    -4    doc/getting-started/building-and-troubleshooting.docbook
M  +3    -3    doc/getting-started/environment.docbook
M  +1    -1    doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/54abdc70cdedf92d3b9b661f012e24c6fee2f412

diff --git a/doc/features/features-overview.docbook b/doc/features/features-overview.docbook
index 7013a51c..41c1cb1c 100644
--- a/doc/features/features-overview.docbook
+++ b/doc/features/features-overview.docbook
@@ -54,7 +54,7 @@ distribution).
 
 <listitem><para>
 &kdesrc-build; does not require a <acronym>GUI</acronym> present to operate. So,
-you can build &kde; without needing an alternate graphical environment.
+you can build &kde; software without needing a graphical environment.
 </para></listitem>
 
 <listitem><para>
diff --git a/doc/getting-started/before-building.docbook b/doc/getting-started/before-building.docbook
index dc6b6277..0390d5fc 100644
--- a/doc/getting-started/before-building.docbook
+++ b/doc/getting-started/before-building.docbook
@@ -25,7 +25,7 @@ does not cover this installation type, since we assume you know what you are doi
 
 </sect2>
 <sect2 id="before-building-preparation">
-<title>Ensure your system is ready to build &kde; source</title>
+<title>Ensure your system is ready to build &kde; software</title>
 
 <para>Before using the &kdesrc-build; script (or any other building
 strategy) you must install the development tools and libraries needed for &kde;.
diff --git a/doc/getting-started/building-and-troubleshooting.docbook b/doc/getting-started/building-and-troubleshooting.docbook
index 71926cc0..95e3c6db 100644
--- a/doc/getting-started/building-and-troubleshooting.docbook
+++ b/doc/getting-started/building-and-troubleshooting.docbook
@@ -8,7 +8,7 @@ it is a good idea to at least load the &kde; project metadata.</para>
 <title>Loading project metadata</title>
 
 <para>
-From a terminal window, log in to the user you are using to compile &kde; and
+From a terminal window, log in to the user you are using to compile &kde; software and
 execute the script:
 </para>
 <screen>
@@ -90,8 +90,8 @@ Your logs are saved in /home/kde-src/kdesrc/log/2018-01-20-07
 
 <para>
 Depending on how many modules you are downloading, it is possible that
-&kdesrc-build; will not succeed the first time you compile &kde;. Do not
-despair!
+&kdesrc-build; will not succeed the first time you compile &kde; software.
+Do not despair!
 </para>
 
 <para>&kdesrc-build; logs the output of every command it runs. By default,
@@ -123,7 +123,7 @@ to mail the <email>kde-devel at kde.org</email> mailing list (subscription may be
 required first) in order to report the build failure.</para>
 
 <para>You can find more common examples of things that can go wrong and their
-solutions, as well as general tips and strategies to build &kde; in the
+solutions, as well as general tips and strategies to build &kde; software in the
 <ulink url="https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source">
 Build from Source</ulink>.
 </para>
diff --git a/doc/getting-started/environment.docbook b/doc/getting-started/environment.docbook
index a1d9f506..6d93a5ce 100644
--- a/doc/getting-started/environment.docbook
+++ b/doc/getting-started/environment.docbook
@@ -2,9 +2,9 @@
 <title>Setting the Environment to Run Your &kde; &plasma; Desktop</title>
 
 <para>
-Assuming you are using a dedicated user to build &kde;, and you already have an
-installed &kde; version, running your new &kde; may be a bit tricky, as the new
-&kde; has to take precedence over the old. You must change the environment
+Assuming you are using a dedicated user to build &kde; &plasma;, and you already have an
+installed &plasma; version, running your new &plasma; may be a bit tricky, as the new
+&plasma; has to take precedence over the old. You must change the environment
 variables of your login scripts to make sure the newly-built desktop is used.
 </para>
 
diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook b/doc/kdesrc-buildrc/conf-options-table.docbook
index 41501ae8..f9875f8f 100644
--- a/doc/kdesrc-buildrc/conf-options-table.docbook
+++ b/doc/kdesrc-buildrc/conf-options-table.docbook
@@ -926,7 +926,7 @@ installed.
 </para>
 
 <para>Note that using this option can have a significant detrimental impact on
-both your bandwidth usage (if you use <replaceable>all</replaceable>) and the time taken to compile &kde;,
+both your bandwidth usage (if you use <replaceable>all</replaceable>) and the time taken to compile &kde; software,
 since &kdesrc-build; will be unable to perform incremental builds.</para>
 </entry>
 </row>