From b6b87a71576a023b81262569aac0d39080fa1feb Mon Sep 17 00:00:00 2001
From: Brian O Grady <brian@codeinstitute.net>
Date: Sun, 4 Aug 2024 11:22:30 +0200
Subject: [PATCH] Updated documentation asks to be mor close aligned with LOs

---
 HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html b/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html
index 85cd30d..e3100ea 100644
--- a/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html
+++ b/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html
@@ -268,17 +268,19 @@ <h3>Environment Setup and Version Control (1 hour)</h3>
                 <li>Document the setup process in the README (Setup and Installation section).</li>
             </ul>
         </li>
-        <li><strong>Associated Criteria:</strong> LO3.2, LO4.6, LO4.9</li>
+        <li><strong>Associated Criteria:</strong> LO3.2, LO4.6, LO4.9, LO5.1</li>
         <li><strong>Pass Grade: Expected Pass Performance (Do's):</strong>
             <ul>
                 <li>Commit regularly to GitHub with meaningful commit messages.</li>
                 <li>Organize files logically from the start.</li>
+                <li>Use consistent and effective markdown formatting to produce a README file in English that is well-structured, easy to follow, and has few grammatical errors. (LO5.1)</li>
             </ul>
         </li>
         <li><strong>Pass Grade Areas for Improvement (Don'ts):</strong>
             <ul>
                 <li>Delay setting up version control.</li>
                 <li>Forget to test the setup to ensure everything is working correctly.</li>
+                <li>Produce a README file with inconsistent formatting or grammatical errors. (LO5.1)</li>
             </ul>
         </li>
     </ul>
@@ -376,6 +378,7 @@ <h3>Must User Stories Implementation (10 hours)</h3>
                 <li>Design must meet accessibility guidelines and have good contrast. (LO1.1)</li>
                 <li>Ensure clear organization of information with headers and prioritized content. (LO1.3)</li>
                 <li>Provide comprehensive documentation of key coding decisions and challenges. (LO2.1, LO4.1)</li>
+                <li>Document any bugs found and their fixes and explanation of any bugs that are left unfixed. (LO2.1)</li>
             </ul>
         </li>
         <li><strong>Merit Grade Areas for Improvement (Don'ts):</strong>
@@ -398,6 +401,7 @@ <h3>Must User Stories Implementation (10 hours)</h3>
                 <li>Provide comprehensive documentation of key coding decisions and challenges. (Comments)</li>
                 <li>Ensure all code is well-structured and adheres to best practices. (Clean Code)</li>
                 <li>Provide a thorough testing report with documented issues and resolutions. (Compliant Code)</li>
+                <li>The solution’s purpose is documented: The purpose of the application is clearly described in the README - key project goals, target audience, screenshots (Real-world application)</li>
             </ul>
         </li>
         <li><strong>Distinction Grade Areas for Improvement (Don'ts):</strong>
@@ -640,6 +644,7 @@ <h3>Documentation (2 hours)</h3>
             <ul>
                 <li>Provide detailed documentation for complex code sections, explaining the choices made and any challenges encountered. (LO4.1, LO4.2)</li>
                 <li>Ensure the README covers all aspects of the project comprehensively. (LO4.3)</li>
+                <li>Document any bugs found and their fixes and explanation of any bugs that are left unfixed. (LO2.1)</li>
             </ul>
         </li>
         <li><strong>Merit Grade Areas for Improvement (Don'ts):</strong>
@@ -651,12 +656,13 @@ <h3>Documentation (2 hours)</h3>
     </div>
 
     <button class="accordion">Show Distinction Guidance</button>
-    <div class="panel">
+    <div class "panel">
         <li><strong>Distinction Grade: Expected Performance (Do's):</strong>
             <ul>
                 <li>Provide detailed documentation for complex code sections, explaining the choices made and any challenges encountered. (Comments)</li>
                 <li>Ensure the README covers all aspects of the project comprehensively. (Readability)</li>
                 <li>The documentation demonstrates a high level of professionalism and attention to detail. (Real-world application)</li>
+                <li>The solution’s purpose is documented: The purpose of the application is clearly described in the README - key project goals, target audience, screenshots (Real-world application)</li>
             </ul>
         </li>
         <li><strong>Distinction Grade Areas for Improvement (Don'ts):</strong>