🏩 fix page nav, remove commented out section 🏩

Author: eformat

docs/3-revenge-of-the-automated-testing/7a-jenkins.md

@@ -92,45 +92,3 @@
     <p class="tip">We should have broken the pipeline and fix these violations in order to continue to our pipeline. Please refer _Here Be Dragons_ section for it.</p>
 
     ![acs-pet-battle-violations](images/acs-pet-battle-violations.png)
-<!--
-## Breaking the Build
-
-Let's run through a scenario where we break/fix the build using a build policy violation.
-
-1. Let's try breaking a *Build Policy* within ACS by triggering the *Build* policy we enabled earlier.
-
-2. Edit the `pet-battle-api/Dockerfile` and add the following line right above last line `CMD`:
-
-    ```bash
-    EXPOSE 22
-    ```
-
-3. Check in this change and watch the build that is triggered.
-
-    ```bash
-    # git add, commit, push your changes..
-    cd /projects/pet-battle
-    git add .
-    git commit -m  "🐉 Expose port 22 🐉"
-    git push
-    ```
-
-4. This should now fail on the image scanning stage:
-
-    ![images/acs-image-fail.png](images/acs-image-fail.png)
-
-5. Back in ACS we can also see the failure in the *Violations* view.
-
-    ![images/acs-violations.png](images/acs-violations.png)
-
-6. Remove the `EXPOSE 22` from the `Dockerfile` and check it in to make the build pass.
-
-    ```bash
-    cd /project/pet-battle
-    git add .
-    git commit -m  "🐧 FIX - Security violation, remove port 22 exposure 🐧"
-    git push
-    ```
-
-🪄 Observe the **pet-battle** pipeline running successfully again.
--->