Fix grammar and styling for FAQ #584
Merged
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
biancabuzea200
approved these changes
Jul 12, 2023
|
I think it would be good to get a Grammarly Pro subscription and to run everything through it |
Hugoo
approved these changes
Jul 12, 2023
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.
Community members and I found some minor issues around grammar and styling.
I would like to suggest proofreading the FAQ pages again now that they got released. There might be further grammar issues down the line that were missed due to the huge PR size. 😁
IMO, we should also not use links within headings and rather put them in the text right under them. The bold blue clickable headlines make it hard to navigate across on mobile phones and conquer the unified look and feel.