Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWill Chandler <wchandler@gitlab.com>2024-01-18 00:57:51 +0300
committerGitLab <noreply@gitlab.com>2024-01-18 00:57:51 +0300
commit72faf14d9551b706f46103d665d75099ea8b1b0c (patch)
tree85abb862a6a39219643585785869aa626964cffb /doc/protobuf.md
parent2f1b99e352ec5c4e270e7ecb9e4234244bf37dee (diff)
parent36339ff6300a2cc727441aa897e2793bd2fcd98a (diff)
Merge branch 'xx/fix-typos' into 'master'
fix: Fix a collection of typos found by typos-cli See merge request https://gitlab.com/gitlab-org/gitaly/-/merge_requests/6594 Merged-by: Will Chandler <wchandler@gitlab.com> Approved-by: Evan Read <eread@gitlab.com> Co-authored-by: Xing Xin <xingxin.xx@bytedance.com>
Diffstat (limited to 'doc/protobuf.md')
-rw-r--r--doc/protobuf.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/protobuf.md b/doc/protobuf.md
index c086caa73..5af7543c9 100644
--- a/doc/protobuf.md
+++ b/doc/protobuf.md
@@ -200,7 +200,7 @@ data inside repositories, so we can rarely assume data to be a Protobuf "string"
### Stream patterns
-Protobuf suppports streaming RPCs which allow for multiple request or response
+Protobuf supports streaming RPCs which allow for multiple request or response
messages to be sent in a single RPC call. We use these whenever it is expected
that an RPC may be invoked with lots of input parameters or when it may generate
a lot of data. This is required by limitations in the gRPC framework where
@@ -320,7 +320,7 @@ To declare the scope, mutators must contain one of the following lines:
tagged with `[(storage)=true]` that indicates the storage's name.
- `option(op_type).scope = REPOSITORY;`: This is the default scoped and thus
doesn't need to be explicitly declared. The associated request must have a
- field tagged with `[(target_repository)=true]` that indcates the repository's
+ field tagged with `[(target_repository)=true]` that indicates the repository's
location.
The target repository represents the location or address of the repository being