typo in "5.2 Distributed Git - Contributing to a Project"

Open
#1,955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

Open book/05-distributed-git/sections/contributing.asc and search for “couple minor changes.” Add the missing “of” so the sentence matches the expected wording, then verify the rendered Distributed Git page shows the correction.

Written by the indexing model from the issue text.

Description

bug
There's no existing/similar bug report.
  • I have searched the existing issues
This report is about a single actionable bug.
  • I'm reporting a single actionable bug
This report is about the ProGit book, version 2, English language.
  • This bug is not about a translation or old version
Bug covers book website/pdf
  • I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
  • This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?

Source files

Describe the bug:

The word "of" is missing from "... Jessica might want to make a couple minor changes to all that merged content, ..." in the file https://github.com/progit/progit2/blob/main/book/05-distributed-git/sections/contributing.asc.

Steps to reproduce:
  1. Go to https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project
  2. Search for "couple minor changes".
  3. See typo
Expected behavior:

I expected the text to say "... Jessica might want to make a couple of minor changes to all that merged content, ...".

Screenshots:

image

Additional context:

No response

Device

laptop

Operating system

No response

Browser/application + version

No response

Dominant language
CSS
Stars
6.6k
Forks
2.1k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from progit/progit2

All issues in progit/progit2

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.