summary refs log tree commit diff
diff options
context:
space:
mode:
authorTobias Geerinckx-Rice <me@tobias.gr>2017-03-14 22:09:06 +0100
committerTobias Geerinckx-Rice <me@tobias.gr>2017-03-15 03:45:55 +0100
commita988cbb766b849854113222cea81c03041540b66 (patch)
tree614efa023c3993b430200b61bf194a934f2982f9
parentd540156c694531c78ca0b9929d992d1c7cdb8e69 (diff)
downloadguix-a988cbb766b849854113222cea81c03041540b66.tar.gz
gnu: stress-make: Fix description.
* gnu/packages/debug.scm (stress-make)[description]: Fix typo.
Avoid ambiguous use of ‘in order’.
-rw-r--r--gnu/packages/debug.scm12
1 files changed, 6 insertions, 6 deletions
diff --git a/gnu/packages/debug.scm b/gnu/packages/debug.scm
index b7d6bbc0eb..6278f661ef 100644
--- a/gnu/packages/debug.scm
+++ b/gnu/packages/debug.scm
@@ -304,12 +304,12 @@ down the road.")
       (home-page "https://github.com/losalamos/stress-make")
       (synopsis "Expose race conditions in Makefiles")
       (description
-       "Stress Make is a customized GNU Make that explicitely managess the
-order in which concurrent jobs are run in order to provoke erroneous behavior
-into becoming manifest.  It can run jobs in the order they're launched, in
-backwards order, or in random order.  The thought is that if code builds
-correctly with Stress Make then it is likely that the @code{Makefile} contains
-no race conditions.")
+       "Stress Make is a customized GNU Make that explicitely manages the order
+in which concurrent jobs are run to provoke erroneous behavior into becoming
+manifest.  It can run jobs in the order in which they're launched, in backwards
+order, or in random order.  The thought is that if code builds correctly with
+Stress Make, then it is likely that the @code{Makefile} contains no race
+conditions.")
       ;; stress-make wrapper is under BSD-3-modifications-must-be-indicated,
       ;; and patched GNU Make is under its own license.
       (license (list (non-copyleft "COPYING.md")