Poorly justified usage recommendation about git pull vs git fetch

[DeinAlptraum]

General overview of your idea.

Chapter 3, section "Remote Branches" contains the following line:
"Generally it’s better to simply use the fetch and merge commands explicitly as the magic of git pull can often be confusing."

This seems out of touch with reality. I don't think I know a single person who does this: it's an unnecessary extra step and git pull isn't that complicated. Using it directly is usually not a problem.
In my opinion, this line should just be removed.

What problem will this solve?

The current text misleads users into suboptimal behavior, and removing it would solve that problem, or at least let them come to their own conclusions based on the facts presented in the chapter.

Have you thought about other solutions?

As an alternative, the section should further elaborate explicitly why git pull is not recommended and what problems it can cause. In any case, the user should be allowed to draw their own conclusion.

Do you want to help with this enhancement idea?

Yes

[ben]

I agree. Want to submit a PR? I'd love for you to get blame credit for the fix.