-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Glossary formatting #191
Comments
I will do that once they are merged. |
@Lokathor also announced they would do it; please coordinate. :) |
Oh I've got enough trouble wrangling |
All right, @ehsanmok it's yours. |
@RalfJung any update on this? |
Oh, this got lost it seems... #153 is still open but overall there was not much PR activity recently, so sorting and formatting it now would be fine I think. |
Closing as not being tracked in the issues in this repo anymore |
(I might make a PR to just do these edits) |
@Lokathor suggested to sort the glossary alphabetically, and I agree that makes sense. We have some PRs in flight that we should land first though, to avoid conflicts.
I am proposing we also change the headers from level 4 to level 3 (
#### Term
to### Term
). Level 4 has the same font size as normal text, so it looks the same as normal bold text, which can be confusing.Open Glossary PRs:
The text was updated successfully, but these errors were encountered: