Skip to content

Typo: seperate → separate #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mojodna wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Typo: seperate → separate #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions text/48_How_Git_Stores_Objects/0_ How_Git_Stores_Objects.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ packed objects.
### Loose Objects ###

Loose objects are the simpler format. It is simply the compressed data stored
in a single file on disk. Every object written to a seperate file.
in a single file on disk. Every object written to a separate file.

If the sha of your object is <code>ab04d884140f7b0cf8bbf86d6883869f16a46f65</code>,
then the file will be stored in the following path:
Expand Down Expand Up @@ -49,7 +49,7 @@ implementation of object storage:
### Packed Objects ###

The other format for object storage is the packfile. Since Git stores each
version of each file as a seperate object, it can get pretty inefficient.
version of each file as a separate object, it can get pretty inefficient.
Imagine having a file several thousand lines long and changing a single line.
Git will store the second file in it's entirety, which is a great big waste
of space.
Expand Down