Merge pull request #20 from cmckee786/patching

Author: TrevorSmale

README.md

@@ -42,7 +42,7 @@ Outlined below are a set of objectives this repository attempts to provide.
 ## To Begin Contributing
 
 ProLUG asks all contributors to understand and adhere to the principles and guidelines detailed
-in the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/src/contributing.md) markdown file.
+in the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/src/contributing.md) markdown file.
 Contributors found significantly deviating from these policies will have their work discarded appropriately.
 
 Contributors will be provided with supplementary material to begin building out unit worksheet labs
@@ -51,12 +51,12 @@ and templates within the project managed issues board.
 To start contributing:
 
 - Understand the repository objectives
-- Read the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/src/contributing.md) markdown
-- Look over the [template pages wiki](https://github.com/ProfessionalLinuxUsersGroup/lac/wiki), or directly here:
-  - Pages: [intro](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/ref/intro.md),
-    [bonus](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/ref/ub.md),
-    [lab](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/ref/ulab.md),
-    [worksheet](https://github.com/ProfessionalLinuxUsersGroup/lac/blob/main/ref/uws.md)
-- Request to be assigned a task within the repo [Issues](https://github.com/ProfessionalLinuxUsersGroup/lac/issues) tab
+- Read the [contributing.md](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/src/contributing.md) markdown
+- Look over the [template pages wiki](https://github.com/ProfessionalLinuxUsersGroup/psc/wiki), or directly here:
+  - Pages: [intro](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/ref/intro.md),
+    [bonus](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/ref/ub.md),
+    [lab](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/ref/ulab.md),
+    [worksheet](https://github.com/ProfessionalLinuxUsersGroup/psc/blob/main/ref/uws.md)
+- Request to be assigned a task within the repo [Issues](https://github.com/ProfessionalLinuxUsersGroup/psc/issues) tab
 - Fork this repository and create a development branch for eventual pull requests
 - Strictly adhere to contemporary GitHub contribution decorum to facilitate the version control process

src/contributing.md

@@ -1,7 +1,7 @@
 <div class="flex-container">
         <img src="https://github.com/ProfessionalLinuxUsersGroup/img/blob/main/Assets/Logos/ProLUG_Round_Transparent_LOGO.png?raw=true" width="64" height="64"></img>
     <p>
-        <h1>Contributing to the ProLUG Linux Sysadmin Course Book</h1>
+        <h1>Contributing to the ProLUG Linux Systems Security Course Book</h1>
     </p>
 </div>
 
@@ -191,21 +191,30 @@ git switch -c unit1-worksheet
 
 Make changes to the `u1ws.md`.
 
-## Understand a few Best Practices
+## Consider a few Useful Practices
 
 ---
 
+The practices presented below are not required to contribute to the ProLUG
+course books but can streamline contributing to any project and are considered
+to some as best practice or incredibly useful when engaging in version control
+with Git.
+
 ### Git Rebasing
 
 <div class="warning">
-  <strong>FIRST AND FOREMOST, ONLY REBASE IN LOCAL REPOSITORIES, NEVER REBASE
+  <strong>FIRST AND FOREMOST, ONLY REBASE IN LOCAL REPOSITORIES. NEVER REBASE
   A PUBLIC BRANCH OR REPOSITORY UNLESS YOU FULLY UNDERSTAND THE CONSEQUENCES.
   YOU HAVE BEEN WARNED.</strong>
 </div>
 
 Proper implementation of rebasing can leave a clean, and easily readable
-commit history for all concerned parties. The Git documentation provides a
-succinct explanation of its utility and how it **could potentially ruin a project**.
+commit history for all concerned parties. Rebasing can also facilitate the
+management of branches and working directories in a notably active project.
+
+The Git documentation provides a succinct explanation of its utility but
+also how it **could potentially ruin a project** and erase the work of other
+contributors.
 
 Rebasing also plays a role in facilitating any commit reverts that may need
 to be made in the future. More on that will follow.