Skip to content

Conversation

@asjarre
Copy link
Contributor

@asjarre asjarre commented Jan 2, 2025

…mat to long format link:

Issue #, if available:

Description of changes:
Fixed the fomatting of the broken links by changing from the <<>> to longer link format link:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@pgasca pgasca self-assigned this Jan 2, 2025
Replaced the external link approach workaround with a fix that allows the preferred cross-reference syntax. Opening inline code with double backticks instead of single backticks was the true source of the problem.
@pgasca pgasca merged commit 5d5bd4d into awsdocs:mainline Jan 3, 2025
1 check failed
@pgasca
Copy link
Contributor

pgasca commented Jan 3, 2025

@asjarre Thank you for your suggestion of an external link workaround, but I found an alternative approach that allows keeping the preferred cross-reference syntax. The problem was elsewhere in the file: opening inline code with double backticks instead of single backticks.

The fix isn't live yet on the public website but should be there for next refresh.

@pgasca pgasca changed the title Fixed the fomatting of the broken links by changing from the <<>> to longer link format link: on the troubleshooting page. Fixed the fomatting of the broken links on the troubleshooting page. Jan 3, 2025
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