Chore: Fix Markdown Syntax Error in Go Documentation#132
Merged
divarvel merged 1 commit intoeclipse-biscuit:mainfrom Jul 15, 2025
Merged
Chore: Fix Markdown Syntax Error in Go Documentation#132divarvel merged 1 commit intoeclipse-biscuit:mainfrom
divarvel merged 1 commit intoeclipse-biscuit:mainfrom
Conversation
ljahier
changed the title
|
I was thinking of doing this PR just to familiarize myself with the project ... glad I looked for open PRs first and see @ljahier's work here! 🎉 |
Contributor
|
good catch, thanks! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
I've identified and corrected a minor error in the markdown syntax that was causing formatting issues in your documentation. After making the necessary corrections, I recompiled the documentation to ensure everything is now displaying as intended. For clarity, I've included two images below: the first one illustrates the problem within the document before the fix, and the second one showcases the corrected and properly formatted document after recompilation.
Before fix:
After fix:
