From af23a4c1f213b7a6356c3098b1bcadd42db3f923 Mon Sep 17 00:00:00 2001 From: Lihua Tang Date: Thu, 20 Sep 2018 10:30:30 +0800 Subject: [PATCH] fix: typo omitted -> ommitted Signed-off-by: Lihua Tang --- api/services/content/v1/content.pb.go | 4 ++-- api/services/content/v1/content.proto | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/api/services/content/v1/content.pb.go b/api/services/content/v1/content.pb.go index b539ae1ae..ec08c3b23 100644 --- a/api/services/content/v1/content.pb.go +++ b/api/services/content/v1/content.pb.go @@ -443,7 +443,7 @@ type ContentClient interface { // Only one active stream may exist at a time for each ref. // // Once a write stream has started, it may only write to a single ref, thus - // once a stream is started, the ref may be ommitted on subsequent writes. + // once a stream is started, the ref may be omitted on subsequent writes. // // For any write transaction represented by a ref, only a single write may // be made to a given offset. If overlapping writes occur, it is an error. @@ -658,7 +658,7 @@ type ContentServer interface { // Only one active stream may exist at a time for each ref. // // Once a write stream has started, it may only write to a single ref, thus - // once a stream is started, the ref may be ommitted on subsequent writes. + // once a stream is started, the ref may be omitted on subsequent writes. // // For any write transaction represented by a ref, only a single write may // be made to a given offset. If overlapping writes occur, it is an error. diff --git a/api/services/content/v1/content.proto b/api/services/content/v1/content.proto index 4f1187145..086b3e39b 100644 --- a/api/services/content/v1/content.proto +++ b/api/services/content/v1/content.proto @@ -55,7 +55,7 @@ service Content { // Only one active stream may exist at a time for each ref. // // Once a write stream has started, it may only write to a single ref, thus - // once a stream is started, the ref may be ommitted on subsequent writes. + // once a stream is started, the ref may be omitted on subsequent writes. // // For any write transaction represented by a ref, only a single write may // be made to a given offset. If overlapping writes occur, it is an error.