Change all registry titles to sentence case

[alexandralloyd]

Describe the issue Change all registry titles to sentence case. Sentence case is "[when] you capitalize just the first letter of the first word in the title. The rest of the words and letters in the title should not be capitalized, unless they're proper nouns."

Rational/Why As a designer, I want all of our product's to align with BC gov web standards. That mean's implementing sentence case in the Platform Registry.

Additional Context It's an accessibility issue and is mandated by the BC Gov web style guide. Capitalization and names in web content: https://www2.gov.bc.ca/gov/content/governments/services-for-government/service-experience-digital-delivery/web-content-development-guides/web-style-guide/writing-guide/capitalization

Here's all the corrections I could find looking at Private Cloud section of the site:

• "Products in Private Cloud OpenShift Platform" to "Products in Private Cloud OpenShift platform"
• "Private Cloud OpenShift Platform" to "Private Cloud OpenShift platform"
• "1. Product Description" to "1. Product description", "Product Name" to "Product name", "Hosting Tier" to "Hosting tier"
• "3. Team Contacts" to "2. Team contacts", "Product Owner Email" to "Product Owner email", "Technical Lead Email" to "Technical Lead email", "First Name" to "First name", "Last Name" to "Last name", "After-Hours Support Contact (optional)" to "After-Hours support contact (optional)"
• "Production Namespace" to "Production namespace", "Tools Namespace" to "Tools namespace", "Development Namespace" to "Development namespace", "Test Namespace" to "Test namespace"
• "4. Common Components" to "4. Common components"

Here's all the corrections to Public Cloud product pages that I could see:

• "1. Product Description" to "1. Product description", "Product Name" to "Product name", "Cloud Services Provider" to "Cloud service provider"
• "Production Account" to "Production account", "Development Account" to "Development account", "Test Account" to "Test account", "Tools Account" to "Tools account"
• "3. Team Contacts" to "2. Team contacts", "Product Owner Email" to "Product Owner email", "Technical Lead Email" to "Technical Lead email", "First Name" to "First name", "Last Name" to "Last name", "After-Hours Support Contact (optional)" to "After-Hours support contact (optional)"
• "Expense Authority Email" to "Expense Authority email", "First Name" to "First name", "Last Name" to "Last name"
• "5. Project Budget" to "5. Project budget", "Estimated average monthly spend - Development Account" to "Estimated average monthly spend - Development account", "Estimated average monthly spend - Test Account" to "Estimated average monthly spend - Test account", "Estimated average monthly spend - Production account" to "Estimated average monthly spend - Production account", "Estimated average monthly spend - Tool Account" to "Estimated average monthly spend - Tool account", "Total Estimated average monthly spend" to "Total estimated average monthly spend"
• 6. Billing (Account Coding) to 6. Billing (Account coding)

Dependencies

• Internal, external, who to talk to if more information is needed

Tests

Definition of done/Acceptance Criteria

• Clear description of the intended final result
• Acceptance criteria that describes the action a User Acceptance Tester would be trying to see if the work is complete

[Iryna-Kaplun]

Hey team! Please add your planning poker estimate with Zenhub @Amritpal-Nijjar @funtigr @golebu2020 @junminahn @Kolezhanchik