From 4ccfdf3fe446cae08ef3e130b88670c8a4723fc2 Mon Sep 17 00:00:00 2001 From: sspencerwire Date: Mon, 2 Jan 2023 08:32:01 -0600 Subject: [PATCH 1/2] # Add space formatting to fix numbered list items --- README.md | 40 ++++++++++++++-------------------------- 1 file changed, 14 insertions(+), 26 deletions(-) diff --git a/README.md b/README.md index 04f98f4539..c5b1949697 100644 --- a/README.md +++ b/README.md @@ -61,53 +61,41 @@ _Add a missing word, correct an error, clarify a confusing bit of text. You won 1. Start on the page you want to update on [https://docs.rockylinux.org/](https://docs.rockylinux.org/). -Click the “Edit” pencil in the upper right corner of the document. You will be taken to the original document stored on GitHub. - -The first time you contribute to the RL repository, you will be prompted with a green button to “**Fork** this **repository** and propose changes.” This creates a duplicate copy of the RL repository where you make your suggested edits. Click the green button and continue. - + Click the “Edit” pencil in the upper right corner of the document. You will be taken to the original document stored on GitHub. + The first time you contribute to the RL repository, you will be prompted with a green button to “**Fork** this **repository** and propose changes.” This creates a duplicate copy of the RL repository where you make your suggested edits. Click the green button and continue. 2. Make your changes -Follow the existing Markdown formatting. Make the necessary change. - - + Follow the existing Markdown formatting. Make the necessary change. 3. Propose changes -At the bottom of the page, write a brief description in the title of the block entitled Propose changes. - -Then click Propose changes, which will **Commit** your changes to a completed document within your forked repository. - + At the bottom of the page, write a brief description in the title of the block entitled Propose changes. + Then click Propose changes, which will **Commit** your changes to a completed document within your forked repository. 4. Review changes -Now you can look at what you’ve done, line by line. If you missed anything, back up to the previous page and correct it again (you’ll have to start over), then click Propose Changes again. - -Once the doc is the way you want it, click the green button that says Create Pull Request. This provides one more chance to double check your changes and confirm the doc is ready. - + Now you can look at what you’ve done, line by line. If you missed anything, back up to the previous page and correct it again (you’ll have to start over), then click Propose Changes again. + Once the doc is the way you want it, click the green button that says Create Pull Request. This provides one more chance to double check your changes and confirm the doc is ready. 5. Create Pull Request -So far you have been working in your own repository. Next you submit it to the documentation team to merge your version into the main version of the document. - -Click the green button that says Create Pull Request, which sends it to the RL documentation team for review. - + So far you have been working in your own repository. Next you submit it to the documentation team to merge your version into the main version of the document. + Click the green button that says Create Pull Request, which sends it to the RL documentation team for review. 6. Wait -Once the RL team reviews your request, they will respond in one of three ways. - - + Once the RL team reviews your request, they will respond in one of three ways. -* Accept and merge your PR -* Comment with feedback and ask for changes -* Deny your PR with explanation + * Accept and merge your PR + * Comment with feedback and ask for changes + * Deny your PR with explanation -If you have to make changes, you will suddenly understand why you need a local repository. The team can [talk you through](https://chat.rockylinux.org/rocky-linux/channels/documentation) what to do next. In good news, it’s still fixable. + If you have to make changes, you will suddenly understand why you need a local repository. The team can [talk you through](https://chat.rockylinux.org/rocky-linux/channels/documentation) what to do next. In good news, it’s still fixable. Need more in-depth explanation? Here are the [same directions](https://docs.google.com/document/d/1Gkwxt3lsxC0HJdLB7YIEMBfPe0td1yVJZ8y5Bjs9oks/edit?usp=sharing) with more words and illustrations. From 2df6e168b088bbd675efdea64f4384cef76972f4 Mon Sep 17 00:00:00 2001 From: sspencerwire Date: Mon, 2 Jan 2023 08:48:11 -0600 Subject: [PATCH 2/2] #fix broken URL's within the all-contributors section --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c5b1949697..7a707962ae 100644 --- a/README.md +++ b/README.md @@ -304,7 +304,7 @@ Welcome aboard! Meet the rest of our awesome contributors below: ([emoji key](ht hopnux
hopnux
🌍 Pedro Garcia Rodriguez
Pedro Garcia Rodriguez
🌍 - Lau
Lau
🖋 + Lau
Lau
🖋 Serge Croisé
Serge Croisé
🖋 bamtests
bamtests
🖋 jahway603
jahway603
🖋 @@ -315,7 +315,7 @@ Welcome aboard! Meet the rest of our awesome contributors below: ([emoji key](ht Laura Hild
Laura Hild
🖋 Grammaresque
Grammaresque
🖋 Brent Dacus
Brent Dacus
🖋 - Rawk Akani
Rawk Akani
🖋 + Rawk Akani
Rawk Akani
🖋