address comments

Author: lventura-codacy

docs/organizations/managing-security-and-risk.md

@@ -681,11 +681,11 @@ Follow our [roadmap](https://roadmap.codacy.com) for updates on this feature.
 
 ## Container scanning {: id="container-scanning"}
 
-Container Scanning is a technique to scan your container image's dependencies for known vulnerabilities. The **Security and risk management > App scanning** page allows you to setup scans that run automatically every night, and surface actionable security findings as new vulnerabilities get discovered.
+Container Scanning is a technique to scan your container image's dependencies for known vulnerabilities. The **Security and risk management > App scanning** page allows you to set up scans that run automatically every night, and surface actionable security findings as new vulnerabilities get discovered.
 
-### How our Container Image Scanning Works
+### How our container image scanning Works
 
-The security tool analyzes your upload SBOM (Software Bill of Materials) files to find vulnerabilities in your container images. An SBOM of a container lists all the dependencies included in the image, which in turn allows the scanner to search for known vulnerabilities (CVEs).
+The security tool analyzes your uploaded SBOM (Software Bill of Materials) files to find vulnerabilities in your container images. An SBOM of a container lists all the dependencies included in the image, which in turn allows the scanner to search for known vulnerabilities (CVEs).
 
 #### High-level flow
 
@@ -702,21 +702,23 @@ No manual action is required to trigger scans after the initial setup.
 
 ### Container scanning setup
 
-You can set up container scanning in one of two ways: by connecting your CI/CD pipeline or by importing your container image manually. Once configured, your image dependencies are scanned daily and results will appear in the Image card list.
+You can set up container scanning in one of two ways: by connecting your CI/CD pipeline or by manually uploading your image SBOM. Once configured, your image dependencies are scanned daily and results will appear in the Image card list.
 
 #### CI/CD Integration
 You must authenticate the Codacy CLI so your pipeline can securely send your image SBOM to Codacy. 
 
 ![Security and risk management import container SBOM in CICD](images/security-risk-management-container-upload-cicd.png)
 
 In order to do that, you need to:
-Get the API token and set up the environment variable as showed in the UI;
-Install and run Codacy CLI in your pipeline to upload results.
+
+1. Get the API token and set up the environment variable as shown in the UI;
+2. Install and run Codacy CLI in your pipeline to upload results.
 
 When CI/CD is configured:
-Images pushed through your pipeline are automatically detected
-New tags are picked up as they are published
-Scans are scheduled automatically
+
+- Images pushed through your pipeline are automatically detected
+- New tags are picked up as they are published
+- Scans are scheduled automatically
 
 This is the recommended setup for continuous coverage.
 
@@ -725,11 +727,11 @@ You can also manually upload your container's Software Bill of Materials (SBOM)
 
 ![Security and risk management manually import container SBOM](images/security-risk-management-container-upload-manually.png)
 
-In order to do manually upload an image, you need to:
+To manually upload an image SBOM, you need to:
 
 1. Add the image name;
 2. Add the image tag;
-3. Upload your container image file(environment and repository fields are optional).
+3. Upload your SBOM file(environment and repository fields are optional).
    !!! note
        You can use the [Codacy CLI v2](https://github.com/codacy/codacy-cli-v2) to generate and upload your SBOM file to Codacy.
 
@@ -762,7 +764,7 @@ Once a tag is scanned, you can click on the `check findings` link to access the
 
 !!! important
     Findings are tied to specific image tags. To resolve a finding, "bump" the tag to a newer version if a fixed version exists (if not, a downgrade or an alternative image may be required). 
-    For dynamic tags such as latest, Codacy will automatically close findings that are no longer present in the current analysis. If you use static tags, you will need to delete tags that are no longer used, as we have a limit of 1000 tags per organization.
+    For dynamic tags such as `latest`, Codacy will automatically close findings that are no longer present in the current analysis. If you use static tags, you will need to delete tags that are no longer used, as we have a limit of 1000 tags per organization.
 
 ### Deleting container image files from Codacy
 
@@ -781,6 +783,7 @@ What happens when you delete an image:
 ### No Results Yet
 
 If there is no last analysis date for an image tag, it means that the SBOM file was received but the scan has not been completed yet. The most likely scenario is that an analysis hasn't been executed yet.
+
 !!! note
-    Remember that scans run nightly (UTC). If you just uploaded the SBOM file, but need results immediately consider using our [Codacy CLI v2](https://github.com/codacy/codacy-cli-v2) to run a local analysis to scan for any issues.
+    Remember that scans run nightly (UTC). If you just uploaded the SBOM file, but need results immediately, consider using our [Codacy CLI v2](https://github.com/codacy/codacy-cli-v2) to run a local analysis to scan for any issues.