Skip to content

Commit

Permalink
Fix spelling issues (paritytech#5206)
Browse files Browse the repository at this point in the history
Hello
I found several spelling errors.
Br, Elias.
  • Loading branch information
nnsW3 authored Aug 12, 2024
1 parent 79e9aa5 commit bc22f08
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions docs/contributor/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,13 @@ The set of labels and their description can be found [here](https://paritytech.g
3. If you’re still working on your PR, please submit as “Draft”. Once a PR is ready for review change the status to
“Open”, so that the maintainers get to review your PR. Generally PRs should sit for 48 hours in order to garner
feedback. It may be merged before if all relevant parties had a look at it.
4. With respect to auditing, please see [AUDIT.md](../AUDIT.md). In general, merging to master can happen independent of
4. With respect to auditing, please see [AUDIT.md](../AUDIT.md). In general, merging to master can happen independently of
audit.
5. PRs will be able to be merged once all reviewers' comments are addressed and CI is successful.

**Noting breaking changes:** When breaking APIs, the PR description should mention what was changed alongside some
examples on how to change the code to make it work/compile. It should also mention potential storage migrations and if
they require some special setup aside adding it to the list of migrations in the runtime.
they require some special setup aside from adding it to the list of migrations in the runtime.

## Reviewing pull requests

Expand Down
4 changes: 2 additions & 2 deletions docs/contributor/DOCUMENTATION_GUIDELINES.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ the `macro@my_macro_name` syntax in your link. Read more about how to correctly

The above five guidelines must always be reasonably respected in the documentation.

The following are a set of notes that may not necessarily hold in all circumstances:
The following is a set of notes that may not necessarily hold in all circumstances:

---

Expand Down Expand Up @@ -205,7 +205,7 @@ properly do this.

## Pallet Crates

The guidelines so far have been general in nature, and are applicable to crates that are pallets and crates that're not
The guidelines so far have been general in nature, and are applicable to crates that are pallets and crates that are not
pallets.

The following is relevant to how to document parts of a crate that is a pallet. See
Expand Down
2 changes: 1 addition & 1 deletion docs/contributor/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ reviewed by reviewers, if the PR does NOT have the `R0-Silent` label. In case of

## Review Notes

*In depth notes about the **implenentation** details of your PR. This should be the main guide for reviewers to
*In depth notes about the **implementation** details of your PR. This should be the main guide for reviewers to
understand your approach and effectively review it. If too long, use
[`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details)*.

Expand Down
2 changes: 1 addition & 1 deletion substrate/docs/SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ required to address security issues.
## Reporting a Vulnerability

Security vulnerabilities in Parity software should be reported by email to [email protected]. If you think your report
might be eligible for the Parity Bug Bounty Program, your email should be send to [email protected].
might be eligible for the Parity Bug Bounty Program, your email should be sent to [email protected].

Your report should include the following:

Expand Down

0 comments on commit bc22f08

Please sign in to comment.