Fix markdown link typo #2438
Merged
Fix markdown link typo #2438
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
The format for a link in one of the markdown documents was inverted so the rendered view was not formatted into a hyperlink. This swaps the `()` and `[]` characters to the correct spots to correct this. Signed-off-by: Sean McGinnis <[email protected]>
etungsten
approved these changes
Sep 19, 2022
zmrow
approved these changes
Sep 19, 2022
ecpullen
approved these changes
Sep 20, 2022
bcressey
approved these changes
Sep 20, 2022
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.
Issue number:
N/A
Description of changes:
The format for a link in one of the markdown documents was inverted so the rendered view was not formatted into a hyperlink. This swaps the
()and[]characters to the correct spots to correct this.Testing done:
Visual inspection.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.