We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This page, https://docs.nginx.com/nginx/deployment-guides/amazon-web-services/route-53-global-server-load-balancing/ has not been revised since April 2018.
You can review and edit the source code for the page directly in our repository. You can edit it directly, as described in Editing files.
Alternatively, if you know Git, you're welcome to fork the repository and use your skills to set up a Pull request.
We need to audit this page.
Here's what we'd like you to do (tasks):
Audit screenshots
Evaluate the page for readability
If you're not (yet) comfortable with Git, you're welcome to post your answers to this issue in a Discussion.
If you haven't been able to do everything in this issue, that's OK. We appreciate all the help that we can get.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This page, https://docs.nginx.com/nginx/deployment-guides/amazon-web-services/route-53-global-server-load-balancing/ has not been revised since April 2018.
You can review and edit the source code for the page directly in our repository. You can edit it directly, as described in Editing files.
Alternatively, if you know Git, you're welcome to fork the repository and use your skills to set up a Pull request.
We need to audit this page.
Here's what we'd like you to do (tasks):
Audit screenshots
Evaluate the page for readability
If you're not (yet) comfortable with Git, you're welcome to post your answers to this issue in a Discussion.
If you haven't been able to do everything in this issue, that's OK. We appreciate all the help that we can get.
The text was updated successfully, but these errors were encountered: