Style consistency: convert bold --> syntax style where necessary
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by searching the documentation for bold formatting used for technical references and compare those occurrences with the repository's syntax-style convention. Review the existing issue comments for any agreed scope or exceptions. Done means the applicable references use consistent syntax styling throughout the docs.
Written by the indexing model from the issue text.
Description
While going through the docs I noticed that bold was used to connote technical references. We should switch that to syntax style instead.
- Dominant language
- Dockerfile
- Stars
- 600
- Forks
- 158
- Avg merge
- 16h 8m
- Merged PRs (30d)
- 21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nunit/docs
-
area:framework
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
area:framework
-
area:framework
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
area:framework
Difficulty 4/5 3-5 days Newbie friendliness 40/100
Similar issues
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Humanity AI Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
numfocus/project-fundraising#166 ·
-
area:proxy bug security severity:low track:open-source
Difficulty 2/5 1-3 hours Newbie friendliness 70/100