Skip to content

Commit 6008483

Browse files
authored
Merge pull request #149 from codecrafters-io/andy/fix
Fix `./git` typos in instructions
2 parents 73842cd + d1084cd commit 6008483

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

course-definition.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -197,10 +197,10 @@ stages:
197197
The path for the object with the hash `e88f7a929cd70b0274c4ea33b209c97fa845fdbc` would be:
198198
199199
```bash
200-
./.git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc
200+
.git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc
201201
```
202202
203-
You'll see that the file isn't placed directly in the `./git/objects` directory. Instead, it's placed in a directory named with the
203+
You'll see that the file isn't placed directly in the `.git/objects` directory. Instead, it's placed in a directory named with the
204204
first two characters of the object's hash. The remaining 38 characters are used as the file name.
205205
206206
Each Git object has its own format for storage. We'll look at how Blobs are stored in this stage, and we'll cover
@@ -548,7 +548,7 @@ stages:
548548
<summary>Click to expand/collapse</summary>
549549
550550
Just like blobs, tree objects are stored in the `.git/objects` directory. If the hash of a tree object is `e88f7a929cd70b0274c4ea33b209c97fa845fdbc`,
551-
the path to the object would be `./git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc`.
551+
the path to the object would be `.git/objects/e8/8f7a929cd70b0274c4ea33b209c97fa845fdbc`.
552552
553553
The format of a tree object file looks like this (after Zlib decompression):
554554

0 commit comments

Comments
 (0)