aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNikita Karetnikov <nikita@karetnikov.org>2013-09-27 08:22:02 +0000
committerNikita Karetnikov <nikita@karetnikov.org>2013-09-27 08:22:02 +0000
commitba7ea5ce335d59d1c990e9204219f000a728c615 (patch)
tree78f68af32167ac2ba6dd2394a275aa1c529131e9 /doc
parentbb5f01c55d6f1d2ab6c9034685de4eba2b0e223a (diff)
downloadguix-ba7ea5ce335d59d1c990e9204219f000a728c615.tar
guix-ba7ea5ce335d59d1c990e9204219f000a728c615.tar.gz
doc: Fix typos.
* doc/guix.texi: Fix typos.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 94658f2b21..196237611e 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -537,9 +537,9 @@ Thus, when installing MPC, the MPFR and GMP libraries also get installed
in the profile; removing MPC also removes MPFR and GMP---unless they had
also been explicitly installed independently.
-Besides, packages sometime rely on the definition of environment
+Besides, packages sometimes rely on the definition of environment
variables for their search paths (see explanation of
-@code{--search-paths} below.) Any missing or possibly incorrect
+@code{--search-paths} below). Any missing or possibly incorrect
environment variable definitions are reported here.
@c XXX: keep me up-to-date
@@ -1838,7 +1838,7 @@ Binutils, libc, and the other packages mentioned above---the
@dfn{bootstrap binaries}.
These bootstrap binaries are ``taken for granted'', though we can also
-re-create them if needed (more on that later.)
+re-create them if needed (more on that later).
@unnumberedsubsec Preparing to Use the Bootstrap Binaries
@@ -1966,7 +1966,7 @@ In practice, there may be some complications. First, it may be that the
extended GNU triplet that specifies an ABI (like the @code{eabi} suffix
above) is not recognized by all the GNU tools. Typically, glibc
recognizes some of these, whereas GCC uses an extra @code{--with-abi}
-configure flag (see @code{gcc.scm} for examples of how to handle this.)
+configure flag (see @code{gcc.scm} for examples of how to handle this).
Second, some of the required packages could fail to build for that
platform. Lastly, the generated binaries could be broken for some
reason.