docs: fix typos

BROWSER-FEATURES.md

@@ -15,7 +15,7 @@ we expect some of those features will evolve too or become deprecated.
   * Access-Control-Allow-Credentials to allow Authorization headers
   * Access-Control-Allow-Methods to allow POST and (preflight) OPTIONS only
   * Access-Control-Allow-Headers to whatever the preflight request carries
-* The client library is epxected to support header overwrites to avoid preflight
+* The client library is expected to support header overwrites to avoid preflight
   * https://github.com/whatwg/fetch/issues/210
 * CSP support to be specified
 

README.md

@@ -190,7 +190,7 @@ var metadata = {'custom-header-1': 'value1'};
 var call = echoService.echo(request, metadata, function(err, response) {
   if (err) {
     console.log(err.code);
-    console.log(err.messge);
+    console.log(err.message);
   } else {
     console.log(response.getMessage());
   }
@@ -205,7 +205,7 @@ call.on('status', function(status) {
 Server-side streaming is supported!
 
 ```js
-var stream = echoService.serverStreamingEcho(streamRequest, metatada);
+var stream = echoService.serverStreamingEcho(streamRequest, metadata);
 stream.on('data', function(response) {
   console.log(response.getMessage());
 });

ROADMAP.md

@@ -20,7 +20,7 @@ users.
 
 Like everywhere, Web platforms and technologies are constantly evolving, often
 with many inter-dependent ecosystems. As much as we like to open-source
-everything, we also need keep the balance bewteen creating a reusable and stable
+everything, we also need keep the balance between creating a reusable and stable
 open-source solution and meeting those requirements unique to Google's Web
 ecosystems or their applications (such as search).