[system/partitionmanager] doc: docbook proofreading

[Marius P]

Git commit e3a996ac6d5b53e34ea0cd2ecbee15548f23db2f by Marius P.
Committed on 23/09/2023 at 22:22.
Pushed by stikonas into branch 'master'.

docbook proofreading

M  +1    -1    doc/faq.docbook
M  +1    -1    doc/glossary.docbook
M  +2    -2    doc/installoshowto.docbook
M  +3    -3    doc/referencemanual.docbook

https://invent.kde.org/system/partitionmanager/-/commit/e3a996ac6d5b53e34ea0cd2ecbee15548f23db2f

diff --git a/doc/faq.docbook b/doc/faq.docbook
index b4e61491..05ea588d 100644
--- a/doc/faq.docbook
+++ b/doc/faq.docbook
@@ -92,7 +92,7 @@
 			</question>
 			<answer>
 				<para>
-					This is a problem of the <command>e2resize</command> command and the underlying ext2/3/4 file system. If a file system is nearly full, <command>e2resize</command> cannot make it any smaller even though that should be possible from the number of free sectors left. &partman; can unfortunately not know beforehand if <command>e2resize</command> will abort with this error for a given file system or not. If it happens nothing will be done at all and your data will not be negatively affected.
+					This is a problem of the <command>e2resize</command> command and the underlying ext2/3/4 file system. If a file system is nearly full, <command>e2resize</command> cannot make it any smaller even though that should be possible from the number of free sectors left. &partman; can unfortunately not know beforehand if <command>e2resize</command> will abort with this error for a given file system or not. If it happens, nothing will be done at all and your data will not be negatively affected.
 				</para>
 				<para>
 					There is no real workaround for this problem right now.
diff --git a/doc/glossary.docbook b/doc/glossary.docbook
index 2f511d6f..20d2d255 100644
--- a/doc/glossary.docbook
+++ b/doc/glossary.docbook
@@ -178,7 +178,7 @@
 		<glossterm>Operation</glossterm>
 		<glossdef>
 			<para>
-				&partman; divides the work it does up in operations, <link linkend="glossary-job">jobs</link> and <link linkend="glossary-command">commands</link>.
+				&partman; divides the work it does into operations, <link linkend="glossary-job">jobs</link> and <link linkend="glossary-command">commands</link>.
 			</para>
 			<para>
 				Operations are the most visible of the three. If you pick an action in the graphical user interface, this will likely result in a new operation being added to the list of pending operations. The idea behind that is: You will most probably want to set up quite a number of steps to transform the current state of your disk devices to the state you have in mind. Some of these steps may take quite a long time to execute (like copying a large file system or resizing a file system that is nearly full). To save you from having to sit in front of your computer for a long time waiting for one step to finish and then starting the next one, operations allow you to exactly specify how the computer's devices should look like once everything is finished, then let &partman; apply the operations and come back when it has executed all of them.
diff --git a/doc/installoshowto.docbook b/doc/installoshowto.docbook
index e9f0e74f..c9436b0d 100644
--- a/doc/installoshowto.docbook
+++ b/doc/installoshowto.docbook
@@ -2,7 +2,7 @@
 	<title>How-To: Installing a New Operating System</title>
 
 	<para>
-		This how-to describes the preparation of a new hard disk device for an OS installation: Suppose you bought a new hard disk and now intend to use it as a replacement for the old one that currently holds your OS and data partitions. You would also like to take this opportunity to install a new operation system. Several steps will have to be taken to make the transition from the old to the new system and drive.
+		This how-to describes the preparation of a new hard disk device for an OS installation: Suppose you bought a new hard disk and now intend to use it as a replacement for the old one that currently holds your OS and data partitions. You would also like to take this opportunity to install a new operating system. Several steps will have to be taken to make the transition from the old to the new system and drive.
 	</para>
 
 	<para>
@@ -125,7 +125,7 @@
 	</para>
 	
 	<para>
-		Your new hard disk device is now ready for the installation of your new operation system.
+		Your new hard disk device is now ready for the installation of your new operating system.
 	</para>
 
 </sect1>
diff --git a/doc/referencemanual.docbook b/doc/referencemanual.docbook
index 4e8266c1..7b26247c 100644
--- a/doc/referencemanual.docbook
+++ b/doc/referencemanual.docbook
@@ -325,7 +325,7 @@
 							<action>Opens a dialog</action> to edit the mount point and the mount options.
 						</para>
 						<para>
-							This command is only enabled if a partition unmounted.
+							This command is only enabled if a partition is unmounted.
 						</para>
 					</listitem>
 				</varlistentry>
@@ -338,7 +338,7 @@
 					</term>
 					<listitem>
 						<para>
-							<action>Mounts or umounts a partition</action>: This command mounts or unmounts the selected partition, depending on its current state.
+							<action>Mounts or unmounts a partition</action>: This command mounts or unmounts the selected partition, depending on its current state.
 						</para>
 						<para>
 							This command is only enabled if a partition is selected that can be mounted or unmounted. If the operating system does not know a mount point for the partition you can not mount it from &partman;.
@@ -373,7 +373,7 @@
 							<action>Backs up a partition</action>: This command backs up the file system on the selected partition to a file. You will be asked where to store the image file after activating this command.
 						</para>
 						<para>
-							The created image file is a sector-for-sector copy of the file system on the partition. It is not compressed and does not have any additional meta information or header added to it, thus it can be directly mounted using a loop device outside of &partman; if the operation system supports that.
+							The created image file is a sector-for-sector copy of the file system on the partition. It is not compressed and does not have any additional meta information or header added to it, thus it can be directly mounted using a loop device outside of &partman; if the operating system supports that.
 						</para>
 						<para>
 							This command is only enabled if a partition is selected and the file system on it can be backed up. The partition must also not be mounted.