docs: use the new [!NOTE] syntax (#10959)

* style-guide: use the new note syntax
* MAINTAINERS: use the new note syntax, use full month names
* CONTRIBUTING: use the new note syntax
* maintainers-guide: use the new note syntax
* CLIENT-SPECIFICATION: use the new note syntax
* COMMUNITY-ROLES: use the new note syntax
* git-terminal: use the new note syntax

---------

Co-authored-by: K.B.Dharun Krishna <kbdharunkrishna@gmail.com>
This commit is contained in:
Lena
2023-10-13 01:26:58 +02:00
committed by GitHub
parent ecee31e62a
commit 7856124245
7 changed files with 33 additions and 23 deletions

View File

@@ -46,8 +46,9 @@ exceptions can always be considered, via open community discussion.)
This means they will be able to
push commits to all of the organization's repositories,
merge PRs, label and close issues, among other things.
_Note_: All members of the tldr-pages organization
must make their membership public.
> [!NOTE]
> All members of the tldr-pages organization
> must make their membership public.
- **Organization members who remain active for a while should become organization owners.**
Specifically: members of the tldr-pages organization
@@ -78,8 +79,9 @@ exceptions can always be considered, via open community discussion.)
## How to change roles
*Note: This section is aimed at owners in the tldr-pages organization
(i.e. the group of people who are able to perform these changes).*
> [!NOTE]
> This section is aimed at owners in the tldr-pages organization
> (i.e. the group of people who are able to perform these changes).*
If you notice a contributor being particularly active,
review their recent contributions to check whether a role transition is due,