docs: another bulk typo correction

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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