Skip to content

docs: fix missing backtick in route list formatting#8073

Merged
zirain merged 1 commit intoenvoyproxy:mainfrom
s20055232:patch-1
Jan 28, 2026
Merged

docs: fix missing backtick in route list formatting#8073
zirain merged 1 commit intoenvoyproxy:mainfrom
s20055232:patch-1

Conversation

@s20055232
Copy link
Copy Markdown
Contributor

Fix formatting: add missing backtick in route list

This commit corrects a markdown formatting error in the route documentation
where foo-route was missing its closing backtick.

The route list now correctly displays:

  • example-route
  • foo-route
  • bar-route

What type of PR is this?

docs: fix formatting in route list

What this PR does / why we need it:

This PR fixes a markdown formatting issue in the route documentation where
foo-route was missing its closing backtick character. This ensures all
route names in the list are consistently formatted as inline code blocks.

Which issue(s) this PR fixes:

Fixes #

Release Notes:

No

@s20055232 s20055232 requested a review from a team as a code owner January 27, 2026 06:52
@netlify
Copy link
Copy Markdown

netlify bot commented Jan 27, 2026

Deploy Preview for cerulean-figolla-1f9435 ready!

Name Link
🔨 Latest commit f7586db
🔍 Latest deploy log https://app.netlify.com/projects/cerulean-figolla-1f9435/deploys/69796da1aca97200085bff83
😎 Deploy Preview https://deploy-preview-8073--cerulean-figolla-1f9435.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Member

@zirain zirain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, can you also fix for v1.6 and latest?

@s20055232
Copy link
Copy Markdown
Contributor Author

Yes, definitely.

@s20055232
Copy link
Copy Markdown
Contributor Author

s20055232 commented Jan 27, 2026

I've created a backport PR for release/v1.6 #8075 . For 'latest', should I target the main branch (which already has the fix)?
Or did you mean something else?"

@zirain
Copy link
Copy Markdown
Member

zirain commented Jan 27, 2026

docs released from main branch, not need to backport to the release branch.

@s20055232
Copy link
Copy Markdown
Contributor Author

Got it, thanks for clarifying! I've closed the backport PR #8075.

@zirain
Copy link
Copy Markdown
Member

zirain commented Jan 27, 2026

can you make same change to the page under site/content/en/v1.6 and site/content/en/latest

@s20055232
Copy link
Copy Markdown
Contributor Author

Oh, my bad! I misunderstood. Fixed it now—could you check again?

@zirain
Copy link
Copy Markdown
Member

zirain commented Jan 27, 2026

can you fix the DCO?

Fix formatting: add missing backtick in route list

This commit corrects a markdown formatting error in the route documentation
where `foo-route` was missing its closing backtick.

The route list now correctly displays:
* `example-route`
* `foo-route`
* `bar-route`

Signed-off-by: ALLEN <s20055232@gmail.com>
@s20055232
Copy link
Copy Markdown
Contributor Author

OK, I fixed it.

Copy link
Copy Markdown
Member

@zirain zirain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@zirain zirain merged commit a1508e6 into envoyproxy:main Jan 28, 2026
26 checks passed
SadmiB pushed a commit to SadmiB/gateway that referenced this pull request Jan 30, 2026
Fix formatting: add missing backtick in route list

This commit corrects a markdown formatting error in the route documentation
where `foo-route` was missing its closing backtick.

The route list now correctly displays:
* `example-route`
* `foo-route`
* `bar-route`

Signed-off-by: ALLEN <s20055232@gmail.com>
Signed-off-by: Sadmi Bouhafs <sadmibouhafs@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants