-Formatted <ul> tags

-Added image: "CYF-Git-Branch-Example.png"

"Git Branches" article:
-Deleted default <p> text; added explanation of Git Branches
-Added hyperlink to "Read more" <a> tag

Author: CraigStodd

Wireframe/CYF-Git-Branch-Example.png

@@ -36,11 +36,17 @@ <h2>README</h2>
           This may include things such as:
 
           <ul>installation instructions</ul>
+
           <ul>Version info</ul>
+
           <ul>System requirements</ul>
+
           <ul>A basic description of the software</ul>
+
           <ul>Troubleshooting and support contact info</ul>
+
           <ul>Copyright and licensing info</ul>
+          
           <ul>Source links</ul>
 
           README files are commonly written in Markdown (.md) plaintext format. 
@@ -51,13 +57,36 @@ <h2>README</h2>
 
         <main>
       <article>
-        <img src="placeholder.svg" alt="" />
+        <img src="CYF-Git-Branch-Example.png" alt="Picture of CYF Example Git Branch Diagram" />
         <h2>Git Branches</h2>
         <p>
-          Lorem ipsum dolor sit amet consectetur adipisicing elit. Quisquam,
-          voluptates. Quisquam, voluptates.
+
+         <ul>In Git, repositories take the form of "branches."</ul>
+
+         <ul>The default branch is called "main" - this represents the original code, developmental history and
+          final version of a project.</ul>
+          
+         <ul>Branches create a copy off of "main" to work on specific issues or parts of a project in isolation.</ul>
+
+         <ul>Individual edits made and saved to a repository are called "commits."</ul>
+
+         <ul>Essentially, a "branch" is a specific sequence of "commits" representing a specific version of a project.</ul>
+
+         <ul>Once finalised, a branch can be merged with the "main" via a "Pull Request"</ul>
+        
+         <br>
+         
+         Branches themselves can also be branched. This allows edits and issues to be specified even further.
+
+         <br>
+         
+         As an example: A user is working on their own branch of a project and identifies issues with two specific areas 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>
-        <a href="https://www.makeareadme.com/">Read more</a>
+        <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</a>
       </article>
     </main>
     <footer>