Incorporated comments from PR

Author: vbakke

README.md

@@ -63,9 +63,9 @@ In case you would like to perform a DevSecOps assessment, the following tools ar
 3. Browse to <http://localhost:8080> (on macOS and Windows browse to <http://192.168.99.100:8080> if you are using docker-machine instead
    of the native docker installation)
 
-For customized DSOMM, take a look at https://github.com/wurstbrot/DevSecOps-MaturityModel-custom. In case you would like to have perform an assessment for multiple teams, iterate from port 8080 to 8XXX, depending of the size of your team.
+For customized DSOMM, take a look at https://github.com/wurstbrot/DevSecOps-MaturityModel-custom. 
 
-You can download your current state from the circular headmap and mount it again via 
+You can download your current state from the circular heatmap and mount it again via 
 
 ```bash
 wget https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/main/src/assets/YAML/generated/generated.yaml # or go to /circular-heatmap and download edited yaml (bottom right)
@@ -129,7 +129,9 @@ In the corresponding [dimension YAMLs](https://github.com/devsecopsmaturitymodel
       teamsEvidence:
         B: All team members completed OWASP Secure Coding Dojo training on 2025-01-11. 
         C: |
-          The pentest report from 2025 has been split into Jira tasks.
+          The pentest report from 2025 has been split into Jira tasks under
+          [TODO-123](https://jira.example.com/issues/TODO-123).
+          
           _2025-04-01:_ All fixes of **critical** findings are deployed to production.
 ```
 The `|` is yaml syntax to indicate that the evidence spans multiple lines. Markdown 

src/assets/Markdown Files/README.md

@@ -63,9 +63,9 @@ In case you would like to perform a DevSecOps assessment, the following tools ar
 3. Browse to <http://localhost:8080> (on macOS and Windows browse to <http://192.168.99.100:8080> if you are using docker-machine instead
    of the native docker installation)
 
-For customized DSOMM, take a look at https://github.com/wurstbrot/DevSecOps-MaturityModel-custom. In case you would like to have perform an assessment for multiple teams, iterate from port 8080 to 8XXX, depending of the size of your team.
+For customized DSOMM, take a look at https://github.com/wurstbrot/DevSecOps-MaturityModel-custom. 
 
-You can download your current state from the circular headmap and mount it again via 
+You can download your current state from the circular heatmap and mount it again via 
 
 ```bash
 wget https://raw.githubusercontent.com/devsecopsmaturitymodel/DevSecOps-MaturityModel-data/main/src/assets/YAML/generated/generated.yaml # or go to /circular-heatmap and download edited yaml (bottom right)
@@ -129,7 +129,9 @@ In the corresponding [dimension YAMLs](https://github.com/devsecopsmaturitymodel
       teamsEvidence:
         B: All team members completed OWASP Secure Coding Dojo training on 2025-01-11. 
         C: |
-          The pentest report from 2025 has been split into Jira tasks.
+          The pentest report from 2025 has been split into Jira tasks under
+          [TODO-123](https://jira.example.com/issues/TODO-123).
+
           _2025-04-01:_ All fixes of **critical** findings are deployed to production.
 ```
 The `|` is yaml syntax to indicate that the evidence spans multiple lines. Markdown 

src/assets/Markdown Files/USAGE.md

@@ -10,8 +10,12 @@ DSOMM is a project of the OWASP Foundation.
 
 **OWASP SAMM** is more focused on the overall maturity of an organization's software assurance and security practices, with a broader scope that includes governance, compliance, risk management, and secure software development.
 
+SAMM is written by security specialists for security specialists, focusing on security processes across the whole organizations.
+
 **DSOMM** focuses on activities that integrate security directly into the DevOps workflows. DSOMM takes a more technical approach, going lower in the technology stack it provides a roadmap on how to systematically improve the security in the software development.
 
+DSOMM is written for technical teams focused on implementing secure software.
+
 DSOMM has currently has a OWASP Lab status, while SAMM has a Flagship status.
 
 # How to use this DSOMM site

src/assets/Markdown Files/dimensions.md

@@ -10,8 +10,6 @@ on the [OWASP Project Integration Project Writeup](https://github.com/OWASP/www-
 
 Secure configuration standards can be enforced during the deployment using the [Open Policy Agent](https://www.openpolicyagent.org/).
 
-![SAMM Release](https://github.com/OWASP/www-project-integration-standards/raw/master/writeups/owasp_in_sdlc/images/samm_release.png "SAMM Release")
-
 **Example Low Maturity scenario:**
 
 The team manually deploys software to production without standardized or automated processes. Secrets, such as passwords and API keys, may have been hardcoded or left in configuration files that are committed to version control, leading to potential exposure and security risks.