2 files changed, 13 insertions(+), 13 deletions(-)

M doc/contributing.texi
M doc/guix.texi

@@ 708,10 708,10 @@ similar development experience and they might work better with the
 tools you currently use or help you make the transition to Emacs.
 
 The options listed below only provide the alternatives to the Emacs
-based setup, which is the most widely used in the Guix community. If
-you want to really understand how is the perfect setup for Guix
-development supposed to work, we encourage you to read the section
-before this regardless the editor you choose to use.
+based setup, which is the most widely used in the Guix community.  If
+you want to really understand how the perfect setup for Guix development
+is supposed to work, we encourage you to read the section before this
+regardless of the editor you choose to use.
 
 @menu
 * Guile Studio::                First step in your transition to Emacs.


@@ 2296,7 2296,7 @@ $ git send-email -@var{NUMBER_COMMITS} -v@var{REVISION} \
 
 If need be, you may use @option{--cover-letter --annotate} to send
 another cover letter, e.g. for explaining what's changed since the last
-revision, and these changes are necessary.
+revision, and why these changes are necessary.
 
 @node Tracking Bugs and Changes
 @section Tracking Bugs and Changes

@@ 1209,7 1209,7 @@ value, configurable via the @code{overload-threshold} field of its
 @code{build-machine} object.
 
 @item
-Disk space availability.  More than a 100 MiB must be available.
+Disk space availability.  More than 100 MiB must be available.
 @end enumerate
 
 The @file{/etc/guix/machines.scm} file typically looks like this:


@@ 12880,7 12880,7 @@ guix repl @var{options} [@var{file} @var{args}]
 @end example
 
 When a @var{file} argument is provided, @var{file} is
-executed as a Guile scripts:
+executed as a Guile script:
 
 @example
 guix repl my-script.scm


@@ 46173,13 46173,13 @@ File name of an additional initrd to load during the boot.  It may or
 may not point to a file in the store, but the main use case is for
 out-of-store files containing secrets.
 
-In order to be able to provide decryption keys for the LUKS device, they
-need to be available in the initial ram disk.  However they cannot be
+In order to be able to provide decryption keys for LUKS devices, they
+need to be available in the initial RAM disk.  However they cannot be
 stored inside the usual initrd, since it is stored in the store and
-being a world-readable (as files in the store are) is not a desired
-property for a initrd containing decryption keys.  You can therefore use
-this field to instruct GRUB to also load a manually created initrd not
-stored in the store.
+being world-readable (as files in the store are) is not a desired
+property for an initrd containing decryption keys.  You can therefore
+use this field to instruct GRUB to also load a manually created initrd
+not stored in the store.
 
 For any use case not involving secrets, you should use regular initrd
 (@pxref{operating-system Reference, @code{initrd}}) instead.