documentation: fix typos in benchmark and auth docs (#8674)

RELEASE NOTES: N/A

Author: eshitachandwani

Documentation/benchmark.md

@@ -24,12 +24,12 @@ that are supported.
 ## Varying Payload Sizes (Weighted Random Distribution)
 
 The `benchmain` utility supports two flags, `-reqPayloadCurveFiles` and
-`-respPayloadCurveFiles`, that can be used to specify a histograms representing
+`-respPayloadCurveFiles`, that can be used to specify histograms representing
 a weighted random distribution of request and response payload sizes,
 respectively. This is useful to simulate workloads with arbitrary payload
 sizes.
 
-The options takes a comma-separated list of file paths as value. Each file must
+The options take a comma-separated list of file paths as value. Each file must
 be a valid CSV file with three columns in each row. Each row represents a range
 of payload sizes (first two columns) and the weight associated with that range
 (third column). For example, consider the below file:

Documentation/grpc-auth-support.md

@@ -1,6 +1,6 @@
 # Authentication
 
-As outlined in the [gRPC authentication guide](https://grpc.io/docs/guides/auth.html) there are a number of different mechanisms for asserting identity between a client and server. We'll present some code-samples here demonstrating how to provide TLS support encryption and identity assertions as well as passing OAuth2 tokens to services that support it.
+As outlined in the [gRPC authentication guide](https://grpc.io/docs/guides/auth.html), there are a number of different mechanisms for asserting identity between a client and server. We'll present some code-samples here demonstrating how to provide TLS support encryption and identity assertions as well as passing OAuth2 tokens to services that support it.
 
 # Enabling TLS on a gRPC client
 
@@ -33,7 +33,7 @@ Clients may use
 to store tokens and other authentication-related data. To gain access to the
 `metadata.MD` object, a server may use
 [metadata.FromIncomingContext](https://godoc.org/google.golang.org/grpc/metadata#FromIncomingContext).
-With a reference to `metadata.MD` on the server, one needs to simply lookup the
+With a reference to `metadata.MD` on the server, one needs to simply look up the
 `authorization` key. Note, all keys stored within `metadata.MD` are normalized
 to lowercase. See [here](https://godoc.org/google.golang.org/grpc/metadata#New).