Skip to content

docs: fix typos and improve accuracy in README.md and contributing guide#281

Open
cluster2600 wants to merge 1 commit intoNVIDIA:masterfrom
cluster2600:docs/fix-readme-typos-and-improve-build-guide
Open

docs: fix typos and improve accuracy in README.md and contributing guide#281
cluster2600 wants to merge 1 commit intoNVIDIA:masterfrom
cluster2600:docs/fix-readme-typos-and-improve-build-guide

Conversation

@cluster2600
Copy link

What

Fix several typos, a factual error, a broken internal link, and minor grammar issues in README.md and docs/contributing.md.

README.md

Line Before After Category
44 the image provide custom builds the image provides custom builds Grammar (subject-verb agreement)
82 you can use the run build.sh`` you can run build.sh`` Grammar (duplicate word)
82 A simple debian build A simple Debian build Style (proper noun)
86 The rpm will be placed in …\.deb The .deb package will be placed in Factual error (example uses --deb, not --rpm)
86 Hardcoded version 2.1.4 in example path <version> placeholder Accuracy (version is stale)
86 can been seen can be seen Grammar

docs/contributing.md

Line Before After Category
7 NVIDIAGPUs NVIDIA GPUs Missing space
57 dcgm_best_practices.md (plain text, wrong filename) [coding_best_practices.md](coding_best_practices.md) (link, correct filename) Broken reference

Why

  • The The rpm will be placed in …\.deb sentence is the most impactful: a first-time contributor building with --deb gets a path description that says "rpm" and an outdated version number. This is confusing and undermines confidence in the build guide.
  • NVIDIAGPUs (no space) reads as a single word in the Contributing introduction; browsers and screen readers handle it poorly.
  • dcgm_best_practices.md does not exist in the repo; the actual file is coding_best_practices.md. A reader following the link (once it becomes a hyperlink) or searching for the file would not find it.

How

All changes are textual — no code, no logic, no tests affected.

Testing

  • grep -n 'rpm will be placed\|can been\|NVIDIAGPUs\|dcgm_best_practices' README.md docs/contributing.md returns no results after the patch
  • Markdown renders correctly in GitHub preview

Checklist

  • Documentation only — no code changes
  • All corrections verified against the actual repo file names and the build.sh output path logic
  • No new dependencies

README.md:
- 'the image provide' → 'the image provides' (subject-verb agreement)
- 'you can use the run build.sh' → 'you can run build.sh' (remove extra word)
- 'A simple debian build' → 'A simple Debian build' (proper noun)
- 'The rpm will be placed in ...\.deb' → 'The .deb package will be placed in'
  (the example command was --deb, not --rpm; the description was wrong)
- Hardcoded version '2.1.4' replaced with '<version>' placeholder to
  avoid misleading readers as the version changes across releases
- 'can been seen' → 'can be seen' (grammar fix)

docs/contributing.md:
- 'NVIDIAGPUs' → 'NVIDIA GPUs' (missing space between brand and noun)
- 'dcgm_best_practices.md' → '[coding_best_practices.md]' with correct
  filename and Markdown hyperlink (the actual file is coding_best_practices.md)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant