docs: Tweak hard link config option description

diff --git a/doc/MANUAL.adoc b/doc/MANUAL.adoc
index 5983b7468fd52d9a8e8900c913adc241f8bdaeed..7ea5f639512964c87065b94b53151f382de904ed 100644 (file)
--- a/doc/MANUAL.adoc
+++ b/doc/MANUAL.adoc
@@ -437,7 +437,7 @@ invocation you can use the `-d`/`--dir` command line option instead.
 
     By default, ccache includes the modification time ("`mtime`") and size of
     the compiler in the hash to ensure that results retrieved from the cache
-    are accurate. If compiler plugins are used, these plugins will also be 
+    are accurate. If compiler plugins are used, these plugins will also be
     added to the hash. This option can be used to select another strategy.
     Possible values are:
 +
@@ -658,11 +658,11 @@ WARNING: Do not enable this option unless you are aware of these caveats:
 * If the resulting file is modified, the file in the cache will also be
   modified since they share content, which corrupts the cache entry. As of
   version 4.0, ccache makes stored and fetched object files read-only as a
-  safety measure guard. Furthermore, a simple integrity check is made for
-  cached object files by verifying that their sizes are correct. This means
-  that mistakes like `strip file.o` or `echo >file.o` will be detected even if
-  the object file is made writeable, but a modification that doesn't change the
-  file size will not.
+  safety measure. Furthermore, a simple integrity check is made for cached
+  object files by verifying that their sizes are correct. This means that
+  mistakes like `strip file.o` or `echo >file.o` will be detected even if the
+  object file is made writeable, but a modification that doesn't change the file
+  size will not.
 * Programs that don't expect that files from two different identical
   compilations are hard links to each other can fail.
 * Programs that rely on modification times (like `make`) can be confused if