docs: another bulk typo correction (#13527)

shollyman · web-flow · commit 90a4f21fc7c1 · 2025-12-30T12:49:10.000-08:00
This PR addresses another bulk README typo (who's -&gt; whose)
diff --git 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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
diff --git a/streetview/README.md b/streetview/README.md
diff --git a/telcoautomation/README.md b/telcoautomation/README.md
diff --git a/vectorsearch/README.md b/vectorsearch/README.md
diff --git a/visionai/README.md b/visionai/README.md
