docs: NGINXaaS for GC docs improvements #1295
Merged
+50
−85
Conversation
This file contains hidden or 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
github-actions
bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
nginx-jack
approved these changes
Oct 13, 2025
amudukutore
approved these changes
Oct 13, 2025
JTorreG
commented
Oct 13, 2025
JTorreG
force-pushed
the
gc/add-landing
branch
from
5dcd60b to
326829a
Compare
tstraley
reviewed
Oct 13, 2025
Co-authored-by: Tim Straley <[email protected]>
tstraley
approved these changes
Oct 13, 2025
puneetsarna
approved these changes
Oct 13, 2025
JTorreG
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Proposed changes
NGINXaaS for GC pre-GA docs improvements
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩