HTML:

- Updated Git Branches explanation.
- Updated README explanation.

Author: CraigStodd

Wireframe/index.html

@@ -40,11 +40,11 @@ <h2>README</h2>
 
         <p>
           The purpose of a README file is to provide important information for a project or piece of software. 
-          This may include things such as:
+          It can include information such as:
         </p>
 
           <ul>
-             <li>instructions</li>
+             <li>Installation/operating instructions</li>
 
             <li>Version info</li>
 
@@ -73,30 +73,24 @@ <h2>README</h2>
 
         <h2>Git Branches</h2>
 
-         <ul>
-          <li>In Git, repositories take the form of "branches."</li>
+        <p>
+           In Git, repositories are made up of "branches."
+        </p>
 
-         <li>The default branch is called "main" - this represents the original code, developmental history and
-          final version of a project.</li>
-          
-         <li>Branches create a copy off of "main" to work on specific issues or parts of a project in isolation.</li>
+         <ul>
+         <li>The the base branch is called "main" - it represents the original code and main development
+          history of a project.</li>
 
-         <li>Individual edits made and saved to a repository are called "commits."</li>
+         <li>When you create a branch from here, you make a copy that can be worked on without messing up 
+          the original code.</li>
 
-         <li>Essentially, a "branch" is a specific sequence of "commits" representing a specific version of a project.</li>
+         <li>Individual edits made and saved to a repository are called "commits," each with their own unique url.</li>
 
-         <li>Once finalised, a branch can be merged with the "main" via a "Pull Request"</li> 
-        </ul>
-         
-         <p>
-          Branches themselves can also be branched. This allows edits and issues to be specified even further.
-        </p>
+         <li>In summary, a "branch" is just a specific sequence of commits - 
+          a timeline of changes made to a project in isolation from the main development.</li>
 
-         <p>
-          As an example: A user is working on their own branch of a project and identifies issues with two specific ares of code, 
-          but the rest of the project is otherwise fine. Individual branches could be created to focus on addressing these
-          problems separately, without worry of accidentally making any drastic changes to the overall project.
-        </p>  
+         <li>Once finalised and, after review, a branch can merged with main development via a "Pull Request."</li> 
+         </ul>
 
         <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">
           READ MORE

Wireframe/style.css

@@ -64,10 +64,12 @@ main {
   margin: 0 auto calc(var(--space) * 4) auto;
 }
 
-header {text-align: center;
+header {
+  text-align: center;
 }
 
-footer {text-align: center;
+footer {
+  text-align: center;
   font-weight: 700;
   border-top-style: solid;
 }
@@ -95,7 +97,6 @@ article {
   border: var(--line);
   padding-bottom: var(--space);
   text-align: justify;
- align-items:center;
   display: grid;
   grid-template-columns: var(--space) 1fr var(--space);
   > * {