Revise titles to Sentence case: NGINX Plus Active-Active HA page

[mjang]

We're in transition from Title Case to Sentence case in our titles. For more info, see our style guide.

Revise all titles on this page accordingly.

• Link to page as built in our docs
• Link to page in the Git repository

You're welcome to revise titles with your Git skills

How to revise this page without Git skills

1. Select the link to the page in the Git repository
2. Find the pencil icon near the top-right of the page
3. Hover over the pencil icon. You may see one of the following messages:
   • "Fork this repository and edit this file"
   • "Edit this file in your fork of this project"
4. Select the option and follow the steps until you see an editable version of this page.
5. Proceed with edits
6. When you're done, select the "Commit changes" button in the upper right part of the page
7. In the Propose changes window that appears, explain what you've done
8. Select Propose changes
9. In the Comparing changes page, review the changes that you're proposing. If you're pleased with what you've done, select "Create pull request"
10. You'll see your pull request! GitHub notifies us on the NGINX Docs team that you've set up a pull request.
11. We'll either accept your pull request or suggest changes. Unless you change default notifications, GitHub will update you at the email address for your GitHub account.
12. Once we've "merged" your pull request, review the result in the "Link to page" location, and celebrate your contribution to Open Source! (It may take several minutes before a merged pull request is reflected at docs.nginx.com.)

[willfranx]

Hi, I'd like to help out with this if that would be alright. Do you assign issues in this project, or should I just go ahead and submit a pull request once I've finished? Thanks!

[mjang]

Hi, I'd like to help out with this if that would be alright. Do you assign issues in this project, or should I just go ahead and submit a pull request once I've finished? Thanks!

Thanks so much for your contribution, @willfranx !

If you have time, we have similar issues in our docs in this major section: https://docs.nginx.com/nginx/deployment-guides/

I haven't had time to set up direct issues on individual pages. But now that you know how to access our repo (and create pull requests), we'd welcome additional contributions!

[willfranx]

You're welcome! I do have time, and if it's alright I'll get to work on those in the next few days. Would it be alright if I just submitted a pull request for the remainder of a section? (For example, the rest of the amazon-web-services directory) Or do you prefer a pull request for each individual page?

[mjang]

You're welcome! I do have time, and if it's alright I'll get to work on those in the next few days. Would it be alright if I just submitted a pull request for the remainder of a section? (For example, the rest of the amazon-web-services directory) Or do you prefer a pull request for each individual page?

Whichever is easier for you.

In general, I lean towards "incremental commits" (aka "one page at a time"), in case someone else is working on other pages.