Skip to content
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

Jump to bottom

Typo fix #45

Merged
merged 1 commit into from
Nov 16, 2023
Merged

Typo fix #45

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
6 changes: 3 additions & 3 deletions draft/ZEP0004.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ The template is intentionally simple.

### Identifying a Convention

In its convention document, a must should declare itself as either an **explicit convention** or a **legacy convention**.
In its convention document, the author must declare the proposal as either an **explicit convention** or a **legacy convention**.

#### Explicit Convention

Expand All @@ -142,7 +142,7 @@ For example, a group metadata JSON document with conventions present might look
}
```

where `units-v1` and `bar` are the convention identifiers.
where `units-v1` and `foo` are the convention identifiers.

#### Legacy Convention

Expand Down Expand Up @@ -264,4 +264,4 @@ This would lead to potentially unlimited scope increases for the zarr core libra
<span property="dct:title">the authors</span></a>
have waived all copyright and related or neighboring rights to
<span property="dct:title">ZEP 4</span>.
</p>
</p>