docs: fix typo in README.md entries

apihub/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

apphub/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

apps/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

backupdr/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

capacityplanner/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

chat/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

chronicle/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

cloudcontrolspartner/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

cloudprofiler/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

cloudquotas/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

configdelivery/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

developerconnect/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

devicestreaming/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

edgenetwork/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

financialservices/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

geminidataanalytics/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

gkerecommender/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

hypercomputecluster/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

identitytoolkit/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

internal/librariangen/configure/_README.md.txt

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

licensemanager/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

locationfinder/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

lustre/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

maintenance/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

managedkafka/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

memorystore/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

modelarmor/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

networkservices/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

oracledatabase/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

parallelstore/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.
 

parametermanager/README.md

@@ -26,7 +26,7 @@ ends in `.../apivXXX`. The `XXX` could be something like `1` or `2` in the case
 of a stable service backend or may be like `1beta2` or `2beta` in the case of a
 more experimental service backend. Because of this fact, a given module can have
 multiple clients for different service backends. In these cases it is generally
-recommend to use clients with stable service backends, with import suffixes like
+recommended to use clients with stable service backends, with import suffixes like
 `apiv1`, unless you need to use features that are only present in a beta backend
 or there is not yet a stable backend available.