[gimp-web] Update index.md. Added a comment to line 99 about not knowing what *Libre* is Edited text in section

[Alexandre Prokoudine <aprokoudine src gnome org>]

commit 00cad7fd66a8d027127483b9f232adf8e3efe1d0
Author: Tom Gooding <panther_ventures telus net>
Date:   Tue Jan 25 01:10:50 2022 +0000

    Update index.md.
    Added a comment to line 99 about not knowing what *Libre* is
    Edited text in section 1. and 3. and 4. and 5.

 content/tutorials/index.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/content/tutorials/index.md b/content/tutorials/index.md
index 887e7e73..9f1e4188 100644
--- a/content/tutorials/index.md
+++ b/content/tutorials/index.md
@@ -96,7 +96,7 @@ You don't have to be a developer to participate to the GIMP project.
 Some team members help with design, community management, bug triaging…
 and some help with documentation and tutorials!
 
-The only thing we ask of contributors is to use *Libre* licenses, which
+The only thing we ask of contributors is to use *Libre* (not sure what a *Libre* license is??, if this is 
meant to say a "Free" license then we should use the word "Free") licenses, which
 allow anyone to share, redistribute and modify the tutorials. It enables
 others to fix tutorials, even years later, even if the original author
 is not around anymore. This is the same rules as for our code, making
@@ -111,26 +111,26 @@ GIMP a Free Software.
 
 So you want to contribute? The process is simple, here is an example for
 the hypothetical case where you found an error in an existing tutorial.
-In such case of editing existing text, your change will be automatically
+In such a case of editing existing text, your change will be automatically
 considered to be in the same license as chosen by the first author:
 
 1. All tutorial contents can be found on our [website's
    repository](https://gitlab.gnome.org/Infrastructure/gimp-web/-/tree/testing/content/tutorials)
-   (*Gitlab*). Feel free to browse to understand the structure: for each
-   tutorial, you have a directory with inside the file `index.md` which
-   contains the text of the tutorial. Many other files can accompany the
-   tutorial inside the directory, such as images, screenshots and
+   (*Gitlab*). After clicking this link, feel free to browse to understand the file structure: Each
+   tutorial is listed in a separate folder and each folder has a file called `index.md` which
+   contains the text of the tutorial. There are many other files that accompany the
+   tutorial inside the folder, such as images, screenshots and
    various assets.
 2. Once you found a tutorial, which you want to edit, click the
    `index.md` link, and you will see a blue button saying "Edit". Click
    it (obviously you need to have created a login first and be
    connected).
 3. *Gitlab* will propose you to "fork" the project because of missing
-   permissions.
-4. Once this is done, fix what needs to be using the
+   permissions.  Press "fork".
+4. Once this is done, make your changes using the
    [Markdown](https://daringfireball.net/projects/markdown/syntax)
-   syntax, as for existing text.
-5. At the bottom of the edit page, notice the "Commit message" field.
+   syntax.
+5. When you are happy with your edits, proceed to the bottom of the edit page, notice the "Commit message" 
field.
    Fill in relevant information explaining what you did. Click "Commit
    changes".
 6. A "New merge request" page will appear. Click "Create merge request".