diff --git a/apihub/README.md b/apihub/README.md index 42ecb4ee3616..3740019dec5c 100644 --- a/apihub/README.md +++ b/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. diff --git a/apphub/README.md b/apphub/README.md index 688d26a4b4e5..4bdcadcebaee 100644 --- a/apphub/README.md +++ b/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. diff --git a/apps/README.md b/apps/README.md index b4d2b40e869b..6c19fc0fad51 100644 --- a/apps/README.md +++ b/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. diff --git a/backupdr/README.md b/backupdr/README.md index da7743a11221..30526d849731 100644 --- a/backupdr/README.md +++ b/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. diff --git a/capacityplanner/README.md b/capacityplanner/README.md index 93126119b1d6..ed22e35e289c 100644 --- a/capacityplanner/README.md +++ b/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. diff --git a/chat/README.md b/chat/README.md index 6a4cc2506f10..b02d946785f7 100644 --- a/chat/README.md +++ b/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. diff --git a/chronicle/README.md b/chronicle/README.md index e9e97ea98f18..527b22e04e1a 100644 --- a/chronicle/README.md +++ b/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. diff --git a/cloudcontrolspartner/README.md b/cloudcontrolspartner/README.md index 14b8f8233a0a..917b80b8ccca 100644 --- a/cloudcontrolspartner/README.md +++ b/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. diff --git a/cloudprofiler/README.md b/cloudprofiler/README.md index d18e8dc6bc34..cecdf165f8ed 100644 --- a/cloudprofiler/README.md +++ b/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. diff --git a/cloudquotas/README.md b/cloudquotas/README.md index d80da21c1d17..bed869c03900 100644 --- a/cloudquotas/README.md +++ b/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. diff --git a/configdelivery/README.md b/configdelivery/README.md index c9b05b29e8b4..50a1293c3b79 100644 --- a/configdelivery/README.md +++ b/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. diff --git a/developerconnect/README.md b/developerconnect/README.md index cb735bf62f9d..99e0aee32f0d 100644 --- a/developerconnect/README.md +++ b/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. diff --git a/devicestreaming/README.md b/devicestreaming/README.md index 3526f3c52b89..a40ea4c39c15 100644 --- a/devicestreaming/README.md +++ b/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. diff --git a/edgenetwork/README.md b/edgenetwork/README.md index 30bb2cbfadac..21f86f3cfc38 100644 --- a/edgenetwork/README.md +++ b/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. diff --git a/financialservices/README.md b/financialservices/README.md index 19bc11d8d46e..2448d016bdf4 100644 --- a/financialservices/README.md +++ b/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. diff --git a/geminidataanalytics/README.md b/geminidataanalytics/README.md index c5fbc6c9335d..87bcd599c9b1 100644 --- a/geminidataanalytics/README.md +++ b/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. diff --git a/gkerecommender/README.md b/gkerecommender/README.md index 5e6ca24ae3c2..11a70c3cca4e 100644 --- a/gkerecommender/README.md +++ b/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. diff --git a/hypercomputecluster/README.md b/hypercomputecluster/README.md index 74836853d807..63dc119421f8 100644 --- a/hypercomputecluster/README.md +++ b/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. diff --git a/identitytoolkit/README.md b/identitytoolkit/README.md index 7d2590d07b4e..ef8a79f2762c 100644 --- a/identitytoolkit/README.md +++ b/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. diff --git a/internal/librariangen/configure/_README.md.txt b/internal/librariangen/configure/_README.md.txt index 1b57b969d946..fc34077fb0fe 100644 --- a/internal/librariangen/configure/_README.md.txt +++ b/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. diff --git a/licensemanager/README.md b/licensemanager/README.md index 612ff73f0f88..32d0a6e56a03 100644 --- a/licensemanager/README.md +++ b/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. diff --git a/locationfinder/README.md b/locationfinder/README.md index 9ae7ebf6e66a..523e03ce8f60 100644 --- a/locationfinder/README.md +++ b/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. diff --git a/lustre/README.md b/lustre/README.md index 245de34f1995..02bae62d9353 100644 --- a/lustre/README.md +++ b/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. diff --git a/maintenance/README.md b/maintenance/README.md index 5b2ddb368c43..1f50c4299744 100644 --- a/maintenance/README.md +++ b/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. diff --git a/managedkafka/README.md b/managedkafka/README.md index 118b52cbbc5d..3607e371335d 100644 --- a/managedkafka/README.md +++ b/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. diff --git a/memorystore/README.md b/memorystore/README.md index 53b70aa783dc..3a04b39ccb47 100644 --- a/memorystore/README.md +++ b/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. diff --git a/modelarmor/README.md b/modelarmor/README.md index 7092c007ef52..b7afb833f2ec 100644 --- a/modelarmor/README.md +++ b/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. diff --git a/networkservices/README.md b/networkservices/README.md index 6c33b50cd985..81fe16b96a7c 100644 --- a/networkservices/README.md +++ b/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. diff --git a/oracledatabase/README.md b/oracledatabase/README.md index 8e214ea331a6..cb8378d1c703 100644 --- a/oracledatabase/README.md +++ b/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. diff --git a/parallelstore/README.md b/parallelstore/README.md index 51576f914143..bb908c5bad13 100644 --- a/parallelstore/README.md +++ b/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. diff --git a/parametermanager/README.md b/parametermanager/README.md index 80cff66f5954..74d2ba14a5eb 100644 --- a/parametermanager/README.md +++ b/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. diff --git a/privilegedaccessmanager/README.md b/privilegedaccessmanager/README.md index c65bb45780ce..71ab26e76722 100644 --- a/privilegedaccessmanager/README.md +++ b/privilegedaccessmanager/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. diff --git a/saasplatform/README.md b/saasplatform/README.md index b7d214ecb579..79e6d5f90cc8 100644 --- a/saasplatform/README.md +++ b/saasplatform/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. diff --git a/securesourcemanager/README.md b/securesourcemanager/README.md index 54da1246b760..5a889add8d7a 100644 --- a/securesourcemanager/README.md +++ b/securesourcemanager/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. diff --git a/securitycentermanagement/README.md b/securitycentermanagement/README.md index fd223bf12cf2..9adcd29cc26b 100644 --- a/securitycentermanagement/README.md +++ b/securitycentermanagement/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. diff --git a/securityposture/README.md b/securityposture/README.md index d8dfa51c108d..50c9005e13bf 100644 --- a/securityposture/README.md +++ b/securityposture/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. diff --git a/servicehealth/README.md b/servicehealth/README.md index c94eb8ed32b9..174b9b826038 100644 --- a/servicehealth/README.md +++ b/servicehealth/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. diff --git a/shopping/README.md b/shopping/README.md index 2a280a49e46b..0308b6c53bed 100644 --- a/shopping/README.md +++ b/shopping/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. diff --git a/storagebatchoperations/README.md b/storagebatchoperations/README.md index 2e22e5b542d9..095903cb22f8 100644 --- a/storagebatchoperations/README.md +++ b/storagebatchoperations/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. diff --git a/streetview/README.md b/streetview/README.md index 17ef157c17eb..887b1f143e8f 100644 --- a/streetview/README.md +++ b/streetview/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. diff --git a/telcoautomation/README.md b/telcoautomation/README.md index 9c20c502a9ca..c61793793ef9 100644 --- a/telcoautomation/README.md +++ b/telcoautomation/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. diff --git a/vectorsearch/README.md b/vectorsearch/README.md index 50035d972640..dbb354d30740 100644 --- a/vectorsearch/README.md +++ b/vectorsearch/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. diff --git a/visionai/README.md b/visionai/README.md index 5cf8cc15dd55..7e2e807c11ff 100644 --- a/visionai/README.md +++ b/visionai/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.