Skip to content
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.

chore: fix typos #588

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -273,7 +273,7 @@ if there are any source or wire incompatible changes. Some notes on this command
Produce a serialized `FileDescriptorSet` for all Protobuf definitions. By default, the serialized
`FileDescriptorSet` is printed to stdout. There are a few options:

- `--include-imports, --include-source-info` are analagous to `protoc`'s `--include_imports,
- `--include-imports, --include-source-info` are analogous to `protoc`'s `--include_imports,
--include_source_info` flags.
- `--json` outputs the FileDescriptorSet as JSON instead of binary.
- `-o` writes the `FileDescriptorSet` to the given output file path.
Expand Down
4 changes: 2 additions & 2 deletions docs/breaking.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ definitions.
### Saved State

If not using git, or you would prefer not to rely on git state to compare your Protobuf definitions
for breaking changes, you can instead save state to a file and use that for comparsion.
for breaking changes, you can instead save state to a file and use that for comparison.

To save your current state:

Expand Down Expand Up @@ -120,7 +120,7 @@ understands the concept of beta vs. stable packages.

If a package's last component is `vMAJORbetaBETA`, where `MAJOR` and `BETA`
are both greater than 0, `prototool break check` will understand that this package is a
beta package, otherwise the package is understood as a stable pacakge.
beta package, otherwise the package is understood as a stable package.

The following are examples of beta packages.

Expand Down
2 changes: 1 addition & 1 deletion docs/protoc.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ this can be done in one of three ways.
commands. The Well-Known Type path should be the directory that includes the `google/protobuf`
directory containing the Well-Known Types.
- By setting the `PROTOTOOL_PROTOC_BIN_PATH` and `PROTOTOOL_PROTOC_WKT_PATH` environment variables,
as we do in the [provided Docker image](docker.md). These variables are analagous to the
as we do in the [provided Docker image](docker.md). These variables are analogous to the
`--protoc-bin-path` and `--protoc-wkt-path` flags, however the flags take precedence.

If any of these options are set, the `protoc.version` option in the `prototool.yaml` file is
Expand Down
2 changes: 1 addition & 1 deletion style/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -1153,7 +1153,7 @@ capitalization.
- `common` - Common has no semantic meaning. See the above discussions on not having common
messages. Use a name that reflects the actual meaning of what you are representing instead.
- `data` - The name "data" is a superfluous decorator. All Protobuf types are data. Use of
"data" also causes singular vs plural issues during iteration, as the singluar of "data" is
"data" also causes singular vs plural issues during iteration, as the singular of "data" is
"datum". If you must have a type that needs such a decorator, use "info" instead.
- `uuid` - We use "id" instead of "uuid" for purposes of consistency. An ID is meant to be
a UUID unless otherwise specified.
Expand Down