Attempt to get Acrolinx > 80

Author: JamesJBarnett

learn-pr/advocates/top-5-security-items-to-consider/3-inputs-and-outputs.yml

@@ -17,7 +17,7 @@ quiz:
 
   - content: "Which of the following data sources need to be validated?"
     choices:
-    - content: "Data from a 3rd party API"
+    - content: "Data from a third-party API"
       isCorrect: false
       explanation: "This is just one of many sources that needs to be validated."
     - content: "Data from the URL parameter"
@@ -34,10 +34,10 @@ quiz:
     choices:
     - content: "They're more organized than inline database commands, and therefore less confusing for users."
       isCorrect: false
-      explanation: "Organization of the code is not the reason that parameterized queries are more secure than inline SQL."
+      explanation: "Organization of the code isn't the reason that parameterized queries are more secure than inline SQL."
     - content: "There's a clear outline of the script in the stored procedure, ensuring better visibility."
       isCorrect: false
-      explanation: "Clear outline of the script is not the reason that parameterized queries are more secure than inline SQL."
+      explanation: "Clear outline of the script isn't the reason that parameterized queries are more secure than inline SQL."
     - content: "Parameterized queries substitute variables before running queries, meaning it avoids the opportunity for code to be submitted in place of a variable."
       isCorrect: true
       explanation: "Parameter fields used in parameterized queries are treated as data, not code, protecting against injection vulnerabilities. For more information on how to implement parameterized queries please see the [OWASP Query Parameterization Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Query_Parameterization_Cheat_Sheet.html)."
@@ -50,9 +50,9 @@ quiz:
     - content: "Data to be output to the screen"
       isCorrect: true
       explanation: "Data sent to the screen needs to be output encoded to ensure it's never interpreted as code."
-    - content: "Data sent to a 3rd party API"
+    - content: "Data sent to a third-party API"
       isCorrect: false
-      explanation: "Although data sent to a 3rd party API needs to be validated to ensure the data is good, we don't need to encode it for output."
+      explanation: "Although data sent to a third-party API needs to be validated to ensure the data is good, we don't need to encode it for output."
     - content: "Data in the URL parameters"
       isCorrect: false
       explanation: "Although data from URL Parameters needs to be validated before it's used in our application, we don't need to encode it for output."