Update database access docs #2526
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jameshochadel
approved these changes
Jul 31, 2024
There was a problem hiding this comment.
Nice — to me, this scans much more easily. Thank you @markdboyd!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
This PR is a fairly significant refactor and reorganization of the documentation on how to access your cloud.gov databases. We get a lot of customer inquiries about how to interact with cloud.gov databases, so my hypothesis is that this information could be better organized. This PR attempts to streamline the information and organize it more logically, for example with clearer headers or a list of steps instead of a wall of text.
Security Considerations
None, hopefully just improving documentation