fix typos on various READMEs (#9459)

bluPhy · kweinmeister · rsamborski · web-flow · commit eba00f1849d3 · 2023-04-13T08:46:40.000-04:00
* Update CONTRIBUTING.md

* Several doc updates

---------

Co-authored-by: Karl Weinmeister &lt;11586922+kweinmeister@users.noreply.github.com&gt;
Co-authored-by: Remigiusz Samborski &lt;rsamborski@users.noreply.github.com&gt;
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -45,4 +45,4 @@ See [AUTHORING_GUIDE.md](AUTHORING_GUIDE.md).
 
 ## Code Reviews
 
-After meeting the above criteria, your code will need to be approved by two reviewers before it can be merged into main. One will be a [CODEOWNER](.github/CODEOWNERS) for the product you are contributing to, and the other will be a repo owner, there to double check for anything that might be detrimental to the overall repo health (things that could cause future tech debt, test flakiness, etc.). Both will automatically be assigned. Some product areas have mulitple folks who can act as the CODEOWNER, and you may be working more closely with a teammate who isn't the automatically assigned reviewer. In that case, it is perfectly fine to manually assign the teammate more familiar with this work as your CODEOWNER reviewer. If you do not hear from your repo owner reviewer within a day (and you know they are not OOO), send them a friendly ping so that you can better understand the review cadence for your PR. All the repo owners are juggling reviews alongside other work, and their velocities can vary, but they are happy to hear from you. If you see that your repo owner reviewer is OOO, you can use the "blunderbuss: assign" label to assign a new reviewer. 
+After meeting the above criteria, your code will need to be approved by two reviewers before it can be merged into main. One will be a [CODEOWNER](.github/CODEOWNERS) for the product you are contributing to, and the other will be a repo owner, there to double check for anything that might be detrimental to the overall repo health (things that could cause future tech debt, test flakiness, etc.). Both will automatically be assigned. Some product areas have multiple folks who can act as the CODEOWNER, and you may be working more closely with a teammate who isn't the automatically assigned reviewer. In that case, it is perfectly fine to manually assign the teammate more familiar with this work as your CODEOWNER reviewer. If you do not hear from your repo owner reviewer within a day (and you know they are not OOO), send them a friendly ping so that you can better understand the review cadence for your PR. All the repo owners are juggling reviews alongside other work, and their velocities can vary, but they are happy to hear from you. If you see that your repo owner reviewer is OOO, you can use the "blunderbuss: assign" label to assign a new reviewer. 
diff --git a/appengine/flexible/twilio/README.md b/appengine/flexible/twilio/README.md
@@ -28,7 +28,7 @@ Refer to the [top-level README](../README.md) for instructions on running and de
 You can run the application locally to test the callbacks and SMS sending. You
 will need to set environment variables before starting your application:
 
-    $ export TWILIO_ACCOUNT_SID=[your-twilio-accoun-sid]
+    $ export TWILIO_ACCOUNT_SID=[your-twilio-account-sid]
     $ export TWILIO_AUTH_TOKEN=[your-twilio-auth-token]
     $ export TWILIO_NUMBER=[your-twilio-number]
     $ python main.py
diff --git a/appengine/flexible_python37_and_earlier/twilio/README.md b/appengine/flexible_python37_and_earlier/twilio/README.md
@@ -28,7 +28,7 @@ Refer to the [top-level README](../README.md) for instructions on running and de
 You can run the application locally to test the callbacks and SMS sending. You
 will need to set environment variables before starting your application:
 
-    $ export TWILIO_ACCOUNT_SID=[your-twilio-accoun-sid]
+    $ export TWILIO_ACCOUNT_SID=[your-twilio-account-sid]
     $ export TWILIO_AUTH_TOKEN=[your-twilio-auth-token]
     $ export TWILIO_NUMBER=[your-twilio-number]
     $ python main.py
diff --git a/composer/rest/README.rst b/composer/rest/README.rst
@@ -108,8 +108,8 @@ To run this sample:
 
     positional arguments:
       project_id            Your Project ID.
-      location              Region of the Cloud Composer environent.
-      composer_environment  Name of the Cloud Composer environent.
+      location              Region of the Cloud Composer environment.
+      composer_environment  Name of the Cloud Composer environment.
 
     optional arguments:
       -h, --help            show this help message and exit
diff --git a/healthcare/api-client/v1/consent/README.rst b/healthcare/api-client/v1/consent/README.rst
@@ -155,7 +155,7 @@ To run this sample:
                             store.
       --export_format {FORMAT_UNSPECIFIED,consent,JSON_BIGQUERY_IMPORT}
                             Specifies the output format. If the format is
-                            unspecified, thedefault functionality is to export to
+                            unspecified, the default functionality is to export to
                             consent.
       --member MEMBER       Member to add to IAM policy (e.g.
                             "domain:example.com")
diff --git a/healthcare/api-client/v1/dicom/README.rst b/healthcare/api-client/v1/dicom/README.rst
@@ -139,15 +139,15 @@ To run this sample:
                             are published on
       --uri_prefix URI_PREFIX
                             URI for a Google Cloud Storage directory to which
-                            result filesshould be written (e.g., "bucket-
+                            result files should be written (e.g., "bucket-
                             id/path/to/destination/dir").
       --content_uri CONTENT_URI
                             URI for a Google Cloud Storage directory from which
-                            filesshould be imported (e.g., "bucket-
+                            files should be imported (e.g., "bucket-
                             id/path/to/destination/dir").
       --export_format {FORMAT_UNSPECIFIED,DICOM,JSON_BIGQUERY_IMPORT}
                             Specifies the output format. If the format is
-                            unspecified, thedefault functionality is to export to
+                            unspecified, the default functionality is to export to
                             DICOM.
       --member MEMBER       Member to add to IAM policy (e.g.
                             "domain:example.com")
diff --git a/iot/api-client/scripts/README.rst b/iot/api-client/scripts/README.rst
@@ -78,7 +78,7 @@ To run this sample:
 
     usage: iam.py [-h] topic_name
 
-    This application demonstrates how programatically grant access to the
+    This application demonstrates how programmatically grant access to the
     Cloud IoT Core service account on a given PubSub topic.
 
     For more information, see https://cloud.google.com/iot.
diff --git a/language/snippets/classify_text/README.rst b/language/snippets/classify_text/README.rst
@@ -9,7 +9,7 @@ Google Cloud Natural Language API Python Samples
 
 This directory contains samples for Google Cloud Natural Language API. The `Google Cloud Natural Language API`_ provides natural language understanding technologies to developers.
 
-This tutorial demostrates how to use the `classify_text` method to classify content category of text files, and use the result to compare texts by their similarity to each other.  See the `tutorial page`_ for details about this sample.
+This tutorial demonstrates how to use the `classify_text` method to classify content category of text files, and use the result to compare texts by their similarity to each other.  See the `tutorial page`_ for details about this sample.
 
 .. _tutorial page: https://cloud.google.com/natural-language/docs/classify-text-tutorial
 

Original file line number	Diff line number	Diff line change
`@@ -45,4 +45,4 @@ See [AUTHORING_GUIDE.md](AUTHORING_GUIDE.md).`
`45`	`45`
`46`	`46`	`## Code Reviews`
`47`	`47`
`48`		-After meeting the above criteria, your code will need to be approved by two reviewers before it can be merged into main. One will be a [CODEOWNER](.github/CODEOWNERS) for the product you are contributing to, and the other will be a repo owner, there to double check for anything that might be detrimental to the overall repo health (things that could cause future tech debt, test flakiness, etc.). Both will automatically be assigned. Some product areas have mulitple folks who can act as the CODEOWNER, and you may be working more closely with a teammate who isn't the automatically assigned reviewer. In that case, it is perfectly fine to manually assign the teammate more familiar with this work as your CODEOWNER reviewer. If you do not hear from your repo owner reviewer within a day (and you know they are not OOO), send them a friendly ping so that you can better understand the review cadence for your PR. All the repo owners are juggling reviews alongside other work, and their velocities can vary, but they are happy to hear from you. If you see that your repo owner reviewer is OOO, you can use the "blunderbuss: assign" label to assign a new reviewer.
	`48`	+After meeting the above criteria, your code will need to be approved by two reviewers before it can be merged into main. One will be a [CODEOWNER](.github/CODEOWNERS) for the product you are contributing to, and the other will be a repo owner, there to double check for anything that might be detrimental to the overall repo health (things that could cause future tech debt, test flakiness, etc.). Both will automatically be assigned. Some product areas have multiple folks who can act as the CODEOWNER, and you may be working more closely with a teammate who isn't the automatically assigned reviewer. In that case, it is perfectly fine to manually assign the teammate more familiar with this work as your CODEOWNER reviewer. If you do not hear from your repo owner reviewer within a day (and you know they are not OOO), send them a friendly ping so that you can better understand the review cadence for your PR. All the repo owners are juggling reviews alongside other work, and their velocities can vary, but they are happy to hear from you. If you see that your repo owner reviewer is OOO, you can use the "blunderbuss: assign" label to assign a new reviewer.