Clarify tree object example not a continuation of previous examples #1630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Alert readers who are following along in the shell that the next example does not use the repository that was just created.
Context
Section 10.2: Git Objects begins with creating a new repository and explaining how blobs are added to it. The active voice used throughout that section implies it is expected for readers to be following along within their own shell. The next section, 10.2: Tree Objects, begins with an example which is not related to the previous examples. The current wording is "most recent tree in a project may look something like this". However, the project created in the previous section is a not a valid interpretation of "a project"; it does not yet have a tree. As a result, readers may enter the command given into their shell and produce an unexpected result:
The topic has just been introduced, so the reader has no understanding from which to make sense of the error. Was it something they did? Is it something else? There is no way for them to know without already understanding the section.
Since the section then continues to use the previously created repository, it seems appropriate to alert readers of the exception in the first example.
This problem has been encountered previously in #421 (fixes #421)