diff --git a/apihub/README.md b/apihub/README.md index 3740019dec5c..dbd519ff772a 100644 --- a/apihub/README.md +++ b/apihub/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/apiregistry/README.md b/apiregistry/README.md index efb1f4967393..e57079c146c7 100644 --- a/apiregistry/README.md +++ b/apiregistry/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/apphub/README.md b/apphub/README.md index 4bdcadcebaee..682b94661aa7 100644 --- a/apphub/README.md +++ b/apphub/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/apps/README.md b/apps/README.md index 6c19fc0fad51..885d4b5a784f 100644 --- a/apps/README.md +++ b/apps/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/backupdr/README.md b/backupdr/README.md index 30526d849731..09bb7612fb73 100644 --- a/backupdr/README.md +++ b/backupdr/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/capacityplanner/README.md b/capacityplanner/README.md index ed22e35e289c..a42431c043e0 100644 --- a/capacityplanner/README.md +++ b/capacityplanner/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/chat/README.md b/chat/README.md index b02d946785f7..afeb7079a5db 100644 --- a/chat/README.md +++ b/chat/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/chronicle/README.md b/chronicle/README.md index 527b22e04e1a..c66cf9877972 100644 --- a/chronicle/README.md +++ b/chronicle/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/cloudcontrolspartner/README.md b/cloudcontrolspartner/README.md index 917b80b8ccca..e586b34a6e35 100644 --- a/cloudcontrolspartner/README.md +++ b/cloudcontrolspartner/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/cloudprofiler/README.md b/cloudprofiler/README.md index cecdf165f8ed..692e43a9c813 100644 --- a/cloudprofiler/README.md +++ b/cloudprofiler/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/cloudquotas/README.md b/cloudquotas/README.md index bed869c03900..5cd033facf53 100644 --- a/cloudquotas/README.md +++ b/cloudquotas/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/configdelivery/README.md b/configdelivery/README.md index 50a1293c3b79..04e4e5f86257 100644 --- a/configdelivery/README.md +++ b/configdelivery/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/developerconnect/README.md b/developerconnect/README.md index 99e0aee32f0d..62cfbbcbe2ab 100644 --- a/developerconnect/README.md +++ b/developerconnect/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/devicestreaming/README.md b/devicestreaming/README.md index a40ea4c39c15..c21b577fcda2 100644 --- a/devicestreaming/README.md +++ b/devicestreaming/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/edgenetwork/README.md b/edgenetwork/README.md index 21f86f3cfc38..b6177f20298a 100644 --- a/edgenetwork/README.md +++ b/edgenetwork/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/financialservices/README.md b/financialservices/README.md index 2448d016bdf4..a8c4e9e1f2fd 100644 --- a/financialservices/README.md +++ b/financialservices/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/geminidataanalytics/README.md b/geminidataanalytics/README.md index 87bcd599c9b1..93e74c436db7 100644 --- a/geminidataanalytics/README.md +++ b/geminidataanalytics/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/gkerecommender/README.md b/gkerecommender/README.md index 11a70c3cca4e..c52234d57793 100644 --- a/gkerecommender/README.md +++ b/gkerecommender/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/hypercomputecluster/README.md b/hypercomputecluster/README.md index 63dc119421f8..c40cb370a6d2 100644 --- a/hypercomputecluster/README.md +++ b/hypercomputecluster/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/identitytoolkit/README.md b/identitytoolkit/README.md index ef8a79f2762c..df27af907bd3 100644 --- a/identitytoolkit/README.md +++ b/identitytoolkit/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/internal/librariangen/configure/_README.md.txt b/internal/librariangen/configure/_README.md.txt index fc34077fb0fe..e24f78bf08bd 100644 --- a/internal/librariangen/configure/_README.md.txt +++ b/internal/librariangen/configure/_README.md.txt @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/licensemanager/README.md b/licensemanager/README.md index 32d0a6e56a03..e7ce89c1fdae 100644 --- a/licensemanager/README.md +++ b/licensemanager/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/locationfinder/README.md b/locationfinder/README.md index 523e03ce8f60..c8a698a3af70 100644 --- a/locationfinder/README.md +++ b/locationfinder/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/lustre/README.md b/lustre/README.md index 02bae62d9353..6b56aa98a5b5 100644 --- a/lustre/README.md +++ b/lustre/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/maintenance/README.md b/maintenance/README.md index 1f50c4299744..5f9a9de40149 100644 --- a/maintenance/README.md +++ b/maintenance/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/managedkafka/README.md b/managedkafka/README.md index 3607e371335d..856688af409c 100644 --- a/managedkafka/README.md +++ b/managedkafka/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/memorystore/README.md b/memorystore/README.md index 3a04b39ccb47..711e9ec878ec 100644 --- a/memorystore/README.md +++ b/memorystore/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/modelarmor/README.md b/modelarmor/README.md index b7afb833f2ec..1f1de1a1924b 100644 --- a/modelarmor/README.md +++ b/modelarmor/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/networkservices/README.md b/networkservices/README.md index 81fe16b96a7c..3ddbd17bac25 100644 --- a/networkservices/README.md +++ b/networkservices/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/oracledatabase/README.md b/oracledatabase/README.md index cb8378d1c703..5ee9b9eac240 100644 --- a/oracledatabase/README.md +++ b/oracledatabase/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/parallelstore/README.md b/parallelstore/README.md index bb908c5bad13..c90714b33437 100644 --- a/parallelstore/README.md +++ b/parallelstore/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/parametermanager/README.md b/parametermanager/README.md index 74d2ba14a5eb..aee3d1f4628c 100644 --- a/parametermanager/README.md +++ b/parametermanager/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/privilegedaccessmanager/README.md b/privilegedaccessmanager/README.md index 71ab26e76722..02e2e310bfd2 100644 --- a/privilegedaccessmanager/README.md +++ b/privilegedaccessmanager/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/saasplatform/README.md b/saasplatform/README.md index 79e6d5f90cc8..26b176571b8a 100644 --- a/saasplatform/README.md +++ b/saasplatform/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/securesourcemanager/README.md b/securesourcemanager/README.md index 5a889add8d7a..28b49c720baa 100644 --- a/securesourcemanager/README.md +++ b/securesourcemanager/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/securitycentermanagement/README.md b/securitycentermanagement/README.md index 9adcd29cc26b..9ae706c90833 100644 --- a/securitycentermanagement/README.md +++ b/securitycentermanagement/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/securityposture/README.md b/securityposture/README.md index 50c9005e13bf..176a2a5b1388 100644 --- a/securityposture/README.md +++ b/securityposture/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/servicehealth/README.md b/servicehealth/README.md index 174b9b826038..c12db609f58e 100644 --- a/servicehealth/README.md +++ b/servicehealth/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/shopping/README.md b/shopping/README.md index 0308b6c53bed..2b0792698ffb 100644 --- a/shopping/README.md +++ b/shopping/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/storagebatchoperations/README.md b/storagebatchoperations/README.md index 095903cb22f8..1c20491f4a35 100644 --- a/storagebatchoperations/README.md +++ b/storagebatchoperations/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/streetview/README.md b/streetview/README.md index 887b1f143e8f..d4a589c7bd3d 100644 --- a/streetview/README.md +++ b/streetview/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/telcoautomation/README.md b/telcoautomation/README.md index c61793793ef9..d2235cbe07f2 100644 --- a/telcoautomation/README.md +++ b/telcoautomation/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/vectorsearch/README.md b/vectorsearch/README.md index dbb354d30740..40cdfb566f08 100644 --- a/vectorsearch/README.md +++ b/vectorsearch/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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 diff --git a/visionai/README.md b/visionai/README.md index 7e2e807c11ff..f901ee374185 100644 --- a/visionai/README.md +++ b/visionai/README.md @@ -21,7 +21,7 @@ However, a `v1+` module may have breaking changes in two scenarios: ### Which package to use? -Generated client library surfaces can be found in packages who's import path +Generated client library surfaces can be found in packages whose import path 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