Apply suggestions from code review

Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
This commit is contained in:
John Ericson 2024-02-12 11:16:12 -05:00 committed by GitHub
parent a34ec0bd12
commit 91557df4a7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions

View file

@ -106,7 +106,7 @@
- [Architecture and Design](architecture/architecture.md) - [Architecture and Design](architecture/architecture.md)
- [Protocols](protocols/index.md) - [Protocols](protocols/index.md)
- [Serving Tarball Flakes](protocols/tarball-fetcher.md) - [Serving Tarball Flakes](protocols/tarball-fetcher.md)
- [Exact Store Path Specification](protocols/store-path.md) - [Store Path Specification](protocols/store-path.md)
- [Derivation "ATerm" file format](protocols/derivation-aterm.md) - [Derivation "ATerm" file format](protocols/derivation-aterm.md)
- [Glossary](glossary.md) - [Glossary](glossary.md)
- [Contributing](contributing/index.md) - [Contributing](contributing/index.md)

View file

@ -47,7 +47,7 @@ where
For either the outputs built from derivations, For either the outputs built from derivations,
paths copied to the store hashed that area single file hashed directly, or the via a hash algorithm other than [SHA-256][sha-256]. paths copied to the store hashed that area single file hashed directly, or the via a hash algorithm other than [SHA-256][sha-256].
(in that case "source" is used; it's silly, but it's done that way for compatibility). (in that case "source" is used; this is only necessary for compatibility).
`<id>` is the name of the output (usually, "out"). `<id>` is the name of the output (usually, "out").
For content-addressed store objects, `<id>`, is always "out". For content-addressed store objects, `<id>`, is always "out".