Skip to content

Commit a4d83f6

Browse files
fix a couple typos in README.md (#2397)
1 parent a51fec8 commit a4d83f6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/Grpc.StatusProto/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ and the [Google APIs overview of the error model](https://cloud.google.com/apis/
3232

3333
## .NET implementation of the richer error model
3434

35-
The error model is define by the protocol buffers files [status.proto](https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto)
35+
The error model is defined by the protocol buffers files [status.proto](https://github.com/googleapis/googleapis/blob/master/google/rpc/status.proto)
3636
and [error_details.proto](https://github.com/googleapis/googleapis/blob/master/google/rpc/error_details.proto),
3737
and the `Google.Api.CommonProtos` NuGet package that provides the generated .NET classes
3838
from these proto files.
@@ -97,7 +97,7 @@ in [grpc/status.h](https://github.com/grpc/grpc/blob/master/include/grpc/status.
9797

9898
The recommendation is to use the values in `Google.Rpc.Code` as a convention.
9999
This is a must for Google APIs and strongly recommended for third party services.
100-
But users can use a different domain of values if they want and and as long as their
100+
But users can use a different domain of values if they want to and as long as their
101101
services are mutually compatible, things will work fine.
102102

103103
In the richer error model the `RpcException` will contain both a `Grpc.Core.Status` (for the

0 commit comments

Comments
 (0)