fixed copy

datawire · Dec 16, 2019 · a697e58 · a697e58
1 parent c5e93fd
commit a697e58
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/reference/core/ambassador.md b/reference/core/ambassador.md
@@ -235,7 +235,7 @@ Ambassador supports bridging HTTP/1.1 clients to backend gRPC servers. When an H
 
 ### gRPC-Web (`enable_grpc_web`)
 
-gRPC is a binary HTTP/2-based protocol that extends the benefits of gRPC to the browser; gRPC-Web wraps around gRPC for clients that cannot speak raw HTTP/2. Though connected, they are distinctly different.
+gRPC-Web is a binary HTTP/2-based protocol that extends the benefits of gRPC to the browser; gRPC-Web wraps around gRPC for clients that cannot speak raw HTTP/2. Though connected, they are distinctly different.
 
 The gRPC-Web specification requires a server-side proxy to translate between gRPC-Web requests and gRPC backend services. Ambassador can serve as the service-side proxy for gRPC-Web when `enable_grpc_web: true` is set. Find more on the gRPC Web client [GitHub](https://github.com/grpc/grpc-web).
 

diff --git a/user-guide/grpc.md b/user-guide/grpc.md
@@ -316,4 +316,4 @@ A simple way around this is to use Ambassador with a `LoadBalancer` service, rat
 
 ## gRPC-Web
 
-gRPC must be configured to work with [gRPC Web](../../reference/core/ambassador#grpc-web-enable_grpc_web) if you want the same benefits in a browser.
+Ambassador also supports the [gRPC-Web](../../reference/core/ambassador#grpc-web-enable_grpc_web) protocol for browser-based gRPC applications.