Capitalize Login.gov (#155)

README.md

@@ -1,7 +1,7 @@
-# login.gov handbook
+# Login.gov handbook
 
-The repository that backs the [login.gov handbook](https://handbook.login.gov/),
-the login.gov team's open source handbook.
+The repository that backs the [Login.gov handbook](https://handbook.login.gov/),
+the Login.gov team's open source handbook.
 
 ## Contributing
 

_articles/accounts.md

@@ -16,13 +16,13 @@ who have admin access to the various services
 
 ## Services
 
-This page lists various services that login.gov team uses to do work.
+This page lists various services that Login.gov team uses to do work.
 
 - Figma
 - Google SearchConsole
 - Hubspot
-- login.gov dashboard
-- login.gov Google Groups
+- Login.gov dashboard
+- Login.gov Google Groups
 - NewRelic
 - NPM Package registry
 - OpsGenie

_articles/appdev-i18n.md

@@ -15,7 +15,7 @@ Content on [secure.login.gov](https://secure.login.gov) and [login.gov](https://
 - French (Canada)
 - Spanish (Mexico)
 
-Translations are requested when content is added or updated on secure.login.gov and login.gov. You can find specific guidance on how to request translations in the [login.gov guidance document](https://docs.google.com/document/d/1-wNXxyvxrsUeHkMOfhBpoSTCTZULOXNlCkBdNxiLa3c/edit).
+Translations are requested when content is added or updated on secure.login.gov and login.gov. You can find specific guidance on how to request translations in the [Login.gov guidance document](https://docs.google.com/document/d/1-wNXxyvxrsUeHkMOfhBpoSTCTZULOXNlCkBdNxiLa3c/edit).
 
 **NOTE:** partners.login.gov and developers.login.gov are not expected to be translated.
 

_articles/appdev-oncall-guide.md

@@ -28,7 +28,7 @@ Rotations:
 
 ## Emergency Contacts
 
-For login.gov and vendor emergency contact information see [Emergency Contacts](https://github.com/18F/identity-devops/wiki/On-Call-Guide-Quick-Reference#emergency-contacts)
+For Login.gov and vendor emergency contact information see [Emergency Contacts](https://github.com/18F/identity-devops/wiki/On-Call-Guide-Quick-Reference#emergency-contacts)
 
 ## Handoff
 
@@ -96,7 +96,7 @@ Involves an active (launched) partner in Production environment
 
 **OR**
 
-* An active (launched) login.gov partner is reporting that no user can authenticate or proof.
+* An active (launched) Login.gov partner is reporting that no user can authenticate or proof.
 * Required to be addressed immediately and ongoing until resolved.
 
 ### Medium severity
@@ -105,7 +105,7 @@ Involves an active (launched) partner in Production environment
 
 **OR**
 
-* An active (Launched) login.gov partner is reporting that some users are not able to authenticate or proof in production.
+* An active (Launched) Login.gov partner is reporting that some users are not able to authenticate or proof in production.
 
 **OR**
 
@@ -124,6 +124,6 @@ Involves an active (launched) partner in Production environment
 * More complicated requests may take longer; expected turnaround should be communicated.
 * On occasion, requests are deemed urgent and should be made a priority.
 
-## Internal login.gov on-call guidance
+## Internal Login.gov on-call guidance
 
-Additional on-call guidance, including time in-lieu is available in the [Internal login.gov on-call guidance Google Doc](https://docs.google.com/document/d/1mOU3rnBJUKiMNFnz-odudmzNCo06CoKsAlCX1ZrK4ZY/edit#)
+Additional on-call guidance, including time in-lieu is available in the [Internal Login.gov on-call guidance Google Doc](https://docs.google.com/document/d/1mOU3rnBJUKiMNFnz-odudmzNCo06CoKsAlCX1ZrK4ZY/edit#)

_articles/appdev-smoketest-debugging.md

@@ -64,7 +64,7 @@ receiving and SMS to confirm deliverability of SMS and email.
 ```
 
 A few of our tests use partner websites (such as USAJOBS in production) to test
-signing in to login.gov. Occasionally those sites go down, and so the smoke tests
+signing in to Login.gov. Occasionally those sites go down, and so the smoke tests
 that use those sites fail.
 
 
@@ -78,5 +78,5 @@ headaches, we choose to rely on partners like this.
 {% include alert.html content=alert_content %}
 
 **What to do**: Check the partner site manually, if it's down, try signing
-in to login.gov through another partner site to make sure things are still up.
+in to Login.gov through another partner site to make sure things are still up.
 

_articles/appdev-troubleshooting-production.md

@@ -8,7 +8,7 @@ category: AppDev
 
 Before you can access any systems, you will need to
  - Obtain a PIV card reader
- - Get cleared for SSH access via PIV into login.gov systems
+ - Get cleared for SSH access via PIV into Login.gov systems
  - [Set up AWS-vault](https://github.com/18F/identity-devops/wiki/Setting-Up-AWS-Vault)
 
 To get SSH access, the public key from your PIV card must be added to the servers you would like to access.

_articles/appdev-troubleshooting-sandbox.md

@@ -1,6 +1,6 @@
 ---
 title: "Troubleshooting the Sandbox"
-description: Troubleshooting issues with the login.gov sandbox/int environment
+description: Troubleshooting issues with the Login.gov sandbox/int environment
 layout: article
 category: AppDev
 ---

_articles/cost-recoverability.md

@@ -2,7 +2,7 @@
 title: Cost Recoverability
 layout: article
 description: |
-  How login.gov is funded and what it means
+  How Login.gov is funded and what it means
 category: Team
 ---
 
@@ -13,11 +13,11 @@ it charges the partner agencies that leverage its services. Login.gov was
 created in 2017 and is still on the path to full cost-recovery, currently
 expected by 2024.
 
-Cost-recoverability has a number of consequences for login.gov. First, it means
+Cost-recoverability has a number of consequences for Login.gov. First, it means
 that it is not our mission to make money, so any cost-savings we achieve will
 ultimately result in lower costs for our partners. It also means that in general
 we are incentivized to operate as efficiently as possible to ensure we can
 achieve and sustain cost-recoverability.
 
-For more information about login.gov's funding and cost-recoverability please
+For more information about Login.gov's funding and cost-recoverability please
 see [All things money](https://docs.google.com/document/d/1bnySzQ8xX3-Q7PHJUDysslwaggoXvDTMlUuRlnI8j0w/edit#).

_articles/definition-of-done.md

@@ -24,7 +24,7 @@ Expect this DoD to change over time.
 - The story is deployed to Dev and/or INT environments
 - Appropriate refactoring has been done as part of developing the story
   - Dead code has been pruned
-  - The login.gov design system is used in views
+  - The Login.gov design system is used in views
 - New code must be free of medium and highlevel static and dynamic security vulnerabilities as reported by Snyk
 - If the story will not be ready to be released to users or there is a serious possibility of failure then the changes are behind a feature flag
 - Analytics logging has been updated and new events have been added if needed

_articles/definition-of-ready.md

@@ -11,12 +11,12 @@ JIRA tickets, and slightly different expectations for each.
 
 ## Stories
 
-Stories are told from user perspectives (where users can't be the login.gov
+Stories are told from user perspectives (where users can't be the Login.gov
 team). They're written in the form *"as **X**, I want to **Y** so that **Z**."*
 For example:
 
 > As a user, I want to provide consent when an SP asks for how current my verified
-> information is, so that I have full control of what login.gov is sharing about me.
+> information is, so that I have full control of what Login.gov is sharing about me.
 
 Often stories list out **AC**s, or **Acceptance Criteria**, for example
 

_articles/deploying-sp-to-prod.md

@@ -18,7 +18,7 @@ Here is a list of items that need to be completed to deploy the configuration fo
 
 2. Ensure that the hubspot deal has been populated with information that comes from [this hubspot template email](https://app.hubspot.com/templates/5531666/edit/13393058). If the email was not sent, then send this template from the hubspot deal to Program Management POC.
 
-3. Ensure that the **Contact Center Fact Sheet** was sent from the hubspot deal. Click on the Emails tab and search for the **"NOTICE: A new login.gov app is launching"** email. If the email was not sent, then send [this template form the hubspot deal](https://app.hubspot.com/templates/5531666/edit/9282726). This template email should go to the [Contact Center Fact Sheet Email List (see handbook appendix)](https://docs.google.com/document/d/1ZMpi7Gj-Og1dn-qUBfQHqLc1Im7rUzDmIxKn11DPJzk/edit#heading=h.2dv73pe5frx0)
+3. Ensure that the **Contact Center Fact Sheet** was sent from the hubspot deal. Click on the Emails tab and search for the **"NOTICE: A new Login.gov app is launching"** email. If the email was not sent, then send [this template form the hubspot deal](https://app.hubspot.com/templates/5531666/edit/9282726). This template email should go to the [Contact Center Fact Sheet Email List (see handbook appendix)](https://docs.google.com/document/d/1ZMpi7Gj-Og1dn-qUBfQHqLc1Im7rUzDmIxKn11DPJzk/edit#heading=h.2dv73pe5frx0)
 
 4. Ensure that the production app has been created on the Dashboard. The partner should be responding with a link to an app in the dashboard with "Production" in the name. The partner may provide the Issuer for the app instead. In this case you can [search for the issuer here](https://dashboard.int.identitysandbox.gov/service_providers/all). You can also check the Dashboard Team URL on the hubspot deal to see if the prod config was created. If not, then [send this template](https://app.hubspot.com/templates/5531666/edit/12106190 ) from the hubspot deal to the Technical POC:
 

_articles/github.md

@@ -7,7 +7,7 @@ category: Development
 
 ## Repositories
 
-View a [list of all repositories](https://github.com/topics/login-gov) tagged for login.gov
+View a [list of all repositories](https://github.com/topics/login-gov) tagged for Login.gov
 
 ### Applications
 
@@ -25,7 +25,7 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
 
 - [**18f/identity-charts**](https://github.com/18f/identity-charts) <br />
   [login-charts-server.app.cloud.gov](https://login-charts-server.app.cloud.gov/)<br />
-  Metrics dashboard for login.gov
+  Metrics dashboard for Login.gov
 
 ### Libraries
 
@@ -36,7 +36,7 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
   Gem that provides functionality for our Ruby applications on our EC2 infrastructure to download secrets and read configs.
 
 - [**18F/omniauth_login_dot_gov**](https://github.com/18F/omniauth_login_dot_gov)
-  Provides an Omniauth strategy for login.gov that helps other projects integrate with login.gov more easily. Some use cases include the [identity-dashboard](https://github.com/18f/identity-dashboard) as well as Touchpoints, USMC and search.gov
+  Provides an Omniauth strategy for Login.gov that helps other projects integrate with Login.gov more easily. Some use cases include the [identity-dashboard](https://github.com/18f/identity-dashboard) as well as Touchpoints, USMC and search.gov
 
 - [**18f/identity-validations**](https://github.com/18f/identity-validations)
   Gem that provides shared validations for the ServiceProvider model across the IDP and dashboard
@@ -79,7 +79,7 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
 ### Design
 
 - [**18f/identity-design-assets**](https://github.com/18f/identity-design-assets)
-  A place for the login.gov design team to version and store design assets (illustrations, sketch files, etc.)
+  A place for the Login.gov design team to version and store design assets (illustrations, sketch files, etc.)
 
 ### Static Sites
 
@@ -91,7 +91,7 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
 - [**18f/identity-style-guide**](https://github.com/18f/identity-style-guide)<br />
   [design.login.gov](https://design.login.gov)<br />
   Hosted on: [Federalist](https://federalistapp.18f.gov/)<br />
-  Walkthrough of login.gov common styles. The respository also hosts the `identity-style-guide` npm package that contains the actual styles.
+  Walkthrough of Login.gov common styles. The respository also hosts the `identity-style-guide` npm package that contains the actual styles.
 
 - [**18f/identity-dev-docs**](https://github.com/18f/identity-dev-docs)<br />
   [developers.login.gov](https://developers.login.gov)<br />
@@ -101,7 +101,7 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
 - [**18f/connect.gov**](https://github.com/18F/connect.gov)<br />
   [connect.gov](https://connect.gov/)<br />
   Hosted on: [Federalist](https://federalistapp.18f.gov/)<br />
-  A site to disambiguate the login.gov's predecessor `connect.gov` from Connecticut's ConnectCT `connect.ct.gov`
+  A site to disambiguate the Login.gov's predecessor `connect.gov` from Connecticut's ConnectCT `connect.ct.gov`
 
 - [**18f/identity-partners-site**](https://github.com/18F/identity-partners-site/pull/1)<br />
   Eventually <https://partners.login.gov> but temporarily preview at <https://cg-23777731-2d5f-44ad-8cd2-5dc27ca6af07.app.cloud.gov/preview/18f/identity-partners-site/initial-content/> <br />
@@ -116,11 +116,11 @@ View a [list of all repositories](https://github.com/topics/login-gov) tagged fo
 - [**18f/identity-handbook-private**](https://github.com/18f/identity-handbook-private) <br />
   [login-handbook.app.cloud.gov](https://login-handbook.app.cloud.gov/)<br />
   Hosted on: [Cloud.gov](https://dashboard.fr.cloud.gov/)<br />
-  Old, private version of this handbook! (Private to login.gov team only)
+  Old, private version of this handbook! (Private to Login.gov team only)
 
 ## Permissions
 
-All login.gov repos should have the following permissions. They can be changed by a current admin under "Settings" > "Manage Access" in Github.
+All Login.gov repos should have the following permissions. They can be changed by a current admin under "Settings" > "Manage Access" in Github.
 
 | Group Name | Role |
 | -----------|------|