update workflow action upload-artifact to v3.1.2

Author: jon gadsden

.github/workflows/ci.yaml

@@ -59,7 +59,7 @@ jobs:
             draft-en.markdown
 
       - name: Save pdfs and epubs
-        uses: actions/upload-artifact@master
+        uses: actions/upload-artifact@v3.1.2
         with:
           name: en-draft
           path: publish
@@ -97,7 +97,7 @@ jobs:
             stable-en.markdown
 
       - name: Save pdfs and epubs
-        uses: actions/upload-artifact@master
+        uses: actions/upload-artifact@v3.1.2
         with:
           name: en-stable
           path: publish
@@ -135,7 +135,7 @@ jobs:
             stable-es.markdown
 
       - name: Save pdfs and epubs
-        uses: actions/upload-artifact@master
+        uses: actions/upload-artifact@v3.1.2
         with:
           name: es-stable
           path: publish

draft-en/02-checklist/05-checklist.md

@@ -273,7 +273,7 @@ tags: SCP-QRG
 - [ ]   All cryptographic functions used to protect secrets from the
     application user must be implemented on a trusted system
 
-- [ ]   Protect master secrets from unauthorized access
+- [ ]   Protect secrets from unauthorized access
 
 - [ ]   Cryptographic modules should fail securely
 
@@ -313,7 +313,7 @@ tags: SCP-QRG
 
 - [ ]   Restrict access to logs to only authorized individuals
 
-- [ ]   Utilize a master routine for all logging operations
+- [ ]   Utilize a central routine for all logging operations
 
 - [ ]   Do not store sensitive information in logs, including unnecessary
     system details, session identifiers or passwords

stable-en/02-checklist/05-checklist.md

@@ -274,7 +274,7 @@ document: OWASP Secure Coding Practices - Quick Reference Guide
 - [ ]   All cryptographic functions used to protect secrets from the
     application user must be implemented on a trusted system
 
-- [ ]   Protect master secrets from unauthorized access
+- [ ]   Protect secrets from unauthorized access
 
 - [ ]   Cryptographic modules should fail securely
 
@@ -314,7 +314,7 @@ document: OWASP Secure Coding Practices - Quick Reference Guide
 
 - [ ]   Restrict access to logs to only authorized individuals
 
-- [ ]   Utilize a master routine for all logging operations
+- [ ]   Utilize a central routine for all logging operations
 
 - [ ]   Do not store sensitive information in logs, including unnecessary
     system details, session identifiers or passwords