Fetch is used in context before being explained

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

Search the Pro Git book source for the occurrences of “fetch” corresponding to pages 51 and 52, then read the surrounding section to identify the first use. Add a short explanation before that use and verify that the wording remains clear in the generated book.

Written by the indexing model from the issue text.

Description

enhancement
General overview of your idea.

While reading the book, I noticed that the term fetch is used (on pages 51 and 52 of the pdf book) before it is actually explained. I think fetch should be explained (at least in a few words) before using it in context.

What problem will this solve?

Readers will better understand the content because they will have an idea of fetch before it is used in context.

Have you thought about other solutions?

No response

Do you want to help with this enhancement idea?

No

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.