02/02: doc: Rename GuixSD to Guix System and remove redundant paragraphs.

[Maxim Cournoyer]

apteryx pushed a commit to branch master
in repository maintenance.

commit eee6e52909c02b15214b2b03410ffbe6b2cb1de8
Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
AuthorDate: Tue Apr 27 11:16:10 2021 -0400

    doc: Rename GuixSD to Guix System and remove redundant paragraphs.
    
    * doc/release.org (Updating the translation files): Remove the
    paragraphs detailing what do when starting from a pristine tree, as
    this is what the 'Bootstrap' section now already covers.
    (Run “make release” for one or several release candidates): Rename
    GuixSD to Guix System.
---
 doc/release.org | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

diff --git a/doc/release.org b/doc/release.org
index 89b7f1e..583692c 100644
--- a/doc/release.org
+++ b/doc/release.org
@@ -69,14 +69,7 @@ is important, and should be re-run anytime you create a new 
tag.
 
 ** Updating the translation files
 
-If running from a pristine checkout, you'll need to run bootstrap and
-configure to have the 'release' target available in the Makefile.
-
-If you already have the 'release' target available, invoking 'make
-release' will automatically invoke ./bootstrap.
-
-Next you will need to fetch, update and commit the translation files,
-if you haven't done so already:
+To fetch, update and commit the translation files, you can run:
 
   $ make download-po
   $ make doc-po-update
@@ -100,8 +93,9 @@ This will automatically build:
   2. The binary tarballs for each architecture, after first updating the
      ~guix~ package in (gnu packages package-management) so that it uses
      the commit above (we’re now at V + 1).
-  3. The GuixSD installation images, after first updating the ~guix~
-     package again to refer to the 2nd commit above (we’re now at V + 2).
+  3. The Guix System installation images, after first updating the
+     ~guix~ package again to refer to the 2nd commit above (we’re now
+     at V + 2).
 
 All these files will end up in a =release-X.Y.Z= sub-directory.