Skip to content

Commit 838e5d6

Browse files
committed
📝 MarkDown formatting quickfix.
1 parent 609020a commit 838e5d6

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ It is better to use similar color styling accross categories for a stronger visu
132132
*Why*
133133
>Red-Orange-Green variations are commonly used internationally to provide a sense of state. Keeping same color styling accross categories is key for a strong and clear visual identification.
134134
135-
**Excelsior Format:**
135+
#### Excelsior Format
136136

137137
```markdown
138138
- `Low`: green
@@ -196,7 +196,7 @@ Labels should help reviewers to quickly get information about the reviewing effo
196196
*Why*
197197
>To provide the consistent information for every issue.
198198
199-
**Excelsior Format:**
199+
#### Excelsior Format
200200

201201
```markdown
202202
- `Caterogy: Type`
@@ -251,6 +251,7 @@ Labels should help reviewers to quickly get information about the reviewing effo
251251

252252
</details>
253253

254+
254255
*Pro tip:* GitHub orders labels aphabetically, so following this format allows to keep categories dislayed in the same order accross every issues.
255256

256257
#### Type Category

0 commit comments

Comments
 (0)