README: Add link to Guix manual and fix syntax.

* README.rst: Add missing newlines for code blocks. Add link to
upstream Guix Packaging Guidelines.

1 files changed, 10 insertions, 1 deletions

diff --git a/README.rst b/README.rst
index b407b83..d5d6915 100644
--- a/README.rst
+++ b/README.rst
@@ -70,14 +70,21 @@ for unfinished contributions with WIP.
 When submitting a new package or a modification to a package, make sure to run:
 
 .. code:: console
+
           guix lint -L /path/to/your/guix/science/checkout <package-name>
 
+This repository follows Guix's `Packaging Guidelines`_, refer to them
+when contributing.
+
+.. _Packaging Guidelines:
+https://guix.gnu.org/manual/devel/en/html_node/Packaging-Guidelines.html
+
 When obtaining a fresh checkout of this repository, run the following
 command:
 
 .. code:: console
 
-   guix git authenticate b1fe5aaff3ab48e798a4cce02f0212bc91f423dc "CA4F 8CF4 37D7 478F DA05  5FD4 4213 7701 1A37 8446"
+          guix git authenticate b1fe5aaff3ab48e798a4cce02f0212bc91f423dc "CA4F 8CF4 37D7 478F DA05  5FD4 4213 7701 1A37 8446"
 
 The command authenticates your checkout and installs Git hooks such that
 ``git pull`` and ``git push`` automatically authenticate it from there
@@ -97,6 +104,7 @@ A new package definition can be added in the relevant module.
 For example, after adding a package definition such as:
 
 .. code:: scheme
+
           (define-public my-package-variable
             (package
               (name "my-package-name")
@@ -105,6 +113,7 @@ For example, after adding a package definition such as:
 can be built using the following command:
 
 .. code:: console
+
           guix build -L /path/to/guix/science/checkout my-package-name
 
 Note that generally the same string is used for the package name and