diff --git a/aws/proposals/github-concerns/README.md b/aws/proposals/github-concerns/README.md
index 3de03ddc..e850eff8 100644
--- a/aws/proposals/github-concerns/README.md
+++ b/aws/proposals/github-concerns/README.md
@@ -112,45 +112,46 @@ The backup process will be implemented using the following approach:
    * Documentation for accessing backups
    * Scripts for bulk restoration if needed
 
-5. GitLab Contingency Planning:
-   As part of our resilience strategy, we need to validate GitLab as a potential temporary alternative during GitHub outages. The following items require setup and validation:
-   
-   * Infrastructure Configuration:
-     * Mirror the GitHub naming convention (replacing "github" with "gitlab" in URLs)
-     * Deploy across the same locations (internal, t26, dmz)
-     * Configure on F5 similar to GitHub Enterprise (even as a single instance)
-     * Validate network access from internal networks, cloud, lab, and mobile devices
-   
-   * Authentication & Access:
-     * LDAP integration:
-       * GUI login functionality
-       * Group synchronization
-     * SAML access for web interface with MFA and Kerberos support
-     * SSH key upload and management process
-     * GPG key upload and verification workflow
-     * Token-based authentication for CLI operations
-   
-   * Repository Management:
-     * Terraform modules for GitLab repository configuration, settings, and teams
-       * Critical for our AWS account baseline management (~300 AWS account repos)
-     * Verification that CODEOWNERS files work as expected
-     * Markdown rendering compatibility check (important for our extensive documentation)
-   
-   * Developer Workflow:
-     * CLI tools for repository operations
-       * Cloning repositories
-       * Creating and managing Merge Requests (GitLab's equivalent to PRs)
-       * Batch operations across multiple repositories (equivalent to git-xargs)
-     * Identify and document necessary workflow adjustments
-   
-   * CI/CD Integration:
-     * OIDC configuration for cloud access via F5 and DMZ instance
-     * Pipeline configuration changes from GitHub Actions to GitLab CI
-   
-   * Communication Strategy:
-     * Documentation updates for development teams
-     * Training materials on GitLab-specific features and terminology
-     * Clear guidance for the transition period
+## GitLab Contingency Planning:
+
+As part of our resilience strategy, we need to validate GitLab as a potential temporary alternative during GitHub outages. The following items require setup and validation:
+
+1. Infrastructure Configuration:
+   1. Mirror the GitHub naming convention (replacing "github" with "gitlab" in URLs)
+   1. Deploy across the same locations (internal, t26, dmz)
+   1. Configure on F5 similar to GitHub Enterprise (even as a single instance)
+   1. Validate network access from internal networks, cloud, lab, and mobile devices
+
+1. Authentication & Access:
+   1. LDAP integration:
+      1. GUI login functionality
+      1. Group synchronization
+   1. SAML access for web interface with MFA and Kerberos support
+   1. SSH key upload and management process
+   1. GPG key upload and verification workflow
+   1. Token-based authentication for CLI operations
+
+1. Repository Management:
+   1. Terraform modules for GitLab repository configuration, settings, and teams
+      1. Critical for our AWS account baseline management (~300 AWS account repos)
+   1. Verification that CODEOWNERS files work as expected
+   1. Markdown rendering compatibility check (important for our extensive documentation)
+
+1. Developer Workflow:
+   1. CLI tools for repository operations
+      1. Cloning repositories
+      1. Creating and managing Merge Requests (GitLab's equivalent to PRs)
+      1. Batch operations across multiple repositories (equivalent to git-xargs)
+   1. Identify and document necessary workflow adjustments
+
+1. CI/CD Integration:
+   1. OIDC configuration for cloud access via F5 and DMZ instance
+   1. Pipeline configuration changes from GitHub Actions to GitLab CI
+
+1. Communication Strategy:
+   1. Documentation updates for development teams
+   1. Training materials on GitLab-specific features and terminology
+   1. Clear guidance for the transition period
 
 ## Tagging
 
@@ -183,3 +184,6 @@ Internal Links:
   - initial proposal
 - 1.1.0 -- 2024-06-22
   - added GitLab contingency planning requirements
+- 1.1.1 -- 2025-05-13
+  - fixed contingency format
+  - where did these dates for 1.0.0 and 1.1.1 come from?