Exclude pattern of test.yml issue:

.github/workflows/test.yml

@@ -28,63 +28,8 @@ jobs:
           file_types: .en.md,.md
           include_files: ${{ steps.changed.outputs.FILES }}
           exclude_patterns: >
-           avatars.githubusercontent.com,
-           example.com,
-           your-server-ip,
-           your-server-hostname,
-           nginx-server,
-           apache-server,
-           site1.com,
-           site2.com,
-           site.com,
-           $releasever,
-           proxy.rocky.lan,
-           repo.rocky.lan,
-           zfs-release,
-           $host$request,
-           fileserver.rockylinux.lan,
-           your_fork_name,
-           rundeck.rockylinux.org,
-           manickathan.ch,
-           breakingpitt.es,
-           download.example,
-           192.168,
-           172.16,
-           127.0.0.1,
-           localhost,
-           download.rockylinux.org,
-           cyber.gov.au,
-           herokuapp.com,
-           rpa.st,
-           home.arpa,
-           SERVER_IP,
-           dev.mysql.com,
-           ip_address,
-           github.com,
-           reddit.com/r/rockylinux,
-           planet.i2p,
-           linode.com,
-           server1.rockylinux.lan,
-           docs.rockylinux.lan,
-           developer.download.nvidia.com,
-           azure.microsoft.com,
-           www.gnu.org,
-           www.samba.org,
-           rsync.samba.org,
-           server.kubernetes.local:6443,
-           node-0:$,0.0.0.0:61208,
-           azuremarketplace.microsoft.com,
-           openqa.rockylinux.org,
-           access.redhat.com,
-           repocompare.rockylinux.org,
-           your_ip,
-           IP:11443,
-           $(hostname):8080,
-           ftp.gnu.org,
-           www.digitalneanderthal.com,
-           mirrors.fedoraproject.org,
-           support.brother.com,
-           www.intel.com
+            avatars.githubusercontent.com, example.com, your-server-ip, your-server-hostname, nginx-server, apache-server, site1.com, site2.com, site.com, $releasever, proxy.rocky.lan, repo.rocky.lan, zfs-release, $host$request, fileserver.rockylinux.lan, your_fork_name, rundeck.rockylinux.org, manickathan.ch, breakingpitt.es, download.example, 192.168, 172.16, 127.0.0.1, localhost, download.rockylinux.org, cyber.gov.au, herokuapp.com, rpa.st, home.arpa, SERVER_IP, dev.mysql.com, ip_address, github.com, reddit.com/r/rockylinux, planet.i2p, linode.com, server1.rockylinux.lan, docs.rockylinux.lan, developer.download.nvidia.com, azure.microsoft.com, www.gnu.org, www.samba.org, rsync.samba.org, server.kubernetes.local:6443, node-0:$,0.0.0.0:61208, azuremarketplace.microsoft.com, openqa.rockylinux.org, access.redhat.com, repocompare.rockylinux.org, your_ip, IP:11443, $(hostname):8080, ftp.gnu.org, www.digitalneanderthal.com, mirrors.fedoraproject.org, support.brother.com, www.intel.com
+
           print_all: false
           retry_count: 1
           timeout: 3

docs/guides/contribute/beginners.md

@@ -11,7 +11,7 @@ tags:
 
 # First-Time Contributor Guide
 
-*Everybody starts somewhere. If this is the first time you have contributed to open source documentation on GitHub, congratulations on taking this step. We can not wait to see what you have to say!*
+*Everybody starts somewhere. If this is the first time you have contributed to open source documentation on GitHub, congratulations on taking this step. We cannot wait to see what you have to say!*
 
 For best results read [our style guide](style_guide.md), which includes several other links to help you learn documentation best practices.
 
@@ -60,44 +60,44 @@ If you're using the `git` command instead of an IDE, you can download the Rocky
 
 1. Start on the page you want to update.
 
-    Click the “Edit” pencil in the upper right corner of the document you want to update. This will take you to the original document on GitHub.
+   Click the “Edit” pencil in the upper right corner of the document you want to update. This will take you to the original document on GitHub.
 
-    The first time you contribute to the Rocky Linux (RL) repository, you will see a prompt 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.
+   The first time you contribute to the Rocky Linux (RL) repository, you will see a prompt 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 Markdown formatting. Perhaps there’s a missing word, or you need to fix the link on line 21, for example. Make the necessary change.
+   Follow the Markdown formatting. Perhaps there’s a missing word, or you need to fix the link on line 21, for example. Make the necessary change.
 
 3. Propose changes
 
-    At the bottom of the page, write a one-line description in the title of the block entitled, “**Propose changes”**. It is helpful, but not necessary, to reference the filename found at the top of the doc.
+   At the bottom of the page, write a one-line description in the title of the block entitled, “**Propose changes”**. It is helpful, but not necessary, to reference the filename found at the top of the doc.
 
-    If you updated a link within line 21 of the markdown text, you might say, "Update README.md with correct links."
+   If you updated a link within line 21 of the markdown text, you might say, "Update README.md with correct links."
 
-    **Note: Word your action in the present tense.**
+   **Note: Word your action in the present tense.**
 
-    Then click Propose changes, which will **Commit** your changes to a complete document within your forked repository.
+   Then click Propose changes, which will **Commit** your changes to a complete document within your forked repository.
 
 4. Review changes
 
-    You can now review your changes, line by line. Did you miss anything? Back up to the previous page and correct it again (you will have to start over), then click Propose Changes again.
+   You can now review your changes, line by line. Did you miss anything? Back up to the previous page and correct it again (you will 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.
+   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 (PR)
 
-    You completed all of your work so far in your own repository, with no opportunity to break the RL main repository. Next, you submit it to the documentation team to merge your version into the main version of the document.
+   You completed all of your work so far in your own repository, with no opportunity to break the RL main repository. Next, you submit it to the documentation team to merge your version into the main version of the document.
 
-    Click the big green button that says Create Pull Request. Good news, you still have not broken anything, because now it goes to the RL documentation team for review.
+   Click the big green button that says Create Pull Request. Good news, you still have not broken anything, because now it goes to the RL documentation team for review.
 
 6. Wait
 
-    Once the RL team gets your request, they will respond in one of three ways.
+   Once the RL team gets 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 an explanation
 
-    The last response is unlikely. We really want to include your perspective here! 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 need to add or change your pull request, a team member will add them to the comment section.
+   The last response is unlikely. We really want to include your perspective here! 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 need to add or change your pull request, a team member will add them to the comment section.
 
-    Otherwise, the team will accept your request and merge it. Welcome to the team, you are officially a contributor now! Look for your name to show up on the all-contributors list at the bottom of the Contributor Guide in a few days.
+   Otherwise, the team will accept your request and merge it. Welcome to the team, you are officially a contributor now! Look for your name to show up on the all-contributors list at the bottom of the Contributor Guide in a few days.