docs: fix various typos in commentary

Google APIs · copybara-github · commit 021fc2e17e44 · 2025-05-29T19:14:36.000-07:00
PiperOrigin-RevId: 764977880
diff --git a/google/cloud/parallelstore/v1beta/parallelstore.proto b/google/cloud/parallelstore/v1beta/parallelstore.proto
@@ -270,8 +270,8 @@ message Instance {
     (google.api.field_behavior) = REQUIRED
   ];
 
-  // Output only. Deprecated 'daos_version' field.
-  // Output only. The version of DAOS software running in the instance.
+  // Output only. Deprecated: The version of DAOS software running in the
+  // instance.
   string daos_version = 9
       [deprecated = true, (google.api.field_behavior) = OUTPUT_ONLY];
 
@@ -345,7 +345,7 @@ message Instance {
 
 // Transfer metadata options for the instance.
 message TransferMetadataOptions {
-  // The UID perservation behavior.
+  // The UID preservation behavior.
   enum Uid {
     // default is UID_NUMBER_PRESERVE.
     UID_UNSPECIFIED = 0;
@@ -473,8 +473,8 @@ message CreateInstanceRequest {
   // ignore the request if it has already been completed. The server will
   // guarantee that for at least 60 minutes since the first request.
   //
-  // For example, consider a situation where you make an initial request and t
-  // he request times out. If you make the request again with the same request
+  // For example, consider a situation where you make an initial request and
+  // the request times out. If you make the request again with the same request
   // ID, the server can check if original operation with the same request ID
   // was received, and if so, will ignore the second request. This prevents
   // clients from accidentally creating duplicate commitments.
@@ -501,8 +501,8 @@ message UpdateInstanceRequest {
   // ignore the request if it has already been completed. The server will
   // guarantee that for at least 60 minutes since the first request.
   //
-  // For example, consider a situation where you make an initial request and t
-  // he request times out. If you make the request again with the same request
+  // For example, consider a situation where you make an initial request and
+  // the request times out. If you make the request again with the same request
   // ID, the server can check if original operation with the same request ID
   // was received, and if so, will ignore the second request. This prevents
   // clients from accidentally creating duplicate commitments.
@@ -527,8 +527,8 @@ message DeleteInstanceRequest {
   // ignore the request if it has already been completed. The server will
   // guarantee that for at least 60 minutes after the first request.
   //
-  // For example, consider a situation where you make an initial request and t
-  // he request times out. If you make the request again with the same request
+  // For example, consider a situation where you make an initial request and
+  // the request times out. If you make the request again with the same request
   // ID, the server can check if original operation with the same request ID
   // was received, and if so, will ignore the second request. This prevents
   // clients from accidentally creating duplicate commitments.
@@ -625,8 +625,8 @@ message ImportDataRequest {
   // ignore the request if it has already been completed. The server will
   // guarantee that for at least 60 minutes since the first request.
   //
-  // For example, consider a situation where you make an initial request and t
-  // he request times out. If you make the request again with the same request
+  // For example, consider a situation where you make an initial request and
+  // the request times out. If you make the request again with the same request
   // ID, the server can check if original operation with the same request ID
   // was received, and if so, will ignore the second request. This prevents
   // clients from accidentally creating duplicate commitments.
@@ -688,8 +688,8 @@ message ExportDataRequest {
   // ignore the request if it has already been completed. The server will
   // guarantee that for at least 60 minutes since the first request.
   //
-  // For example, consider a situation where you make an initial request and t
-  // he request times out. If you make the request again with the same request
+  // For example, consider a situation where you make an initial request and
+  // the request times out. If you make the request again with the same request
   // ID, the server can check if original operation with the same request ID
   // was received, and if so, will ignore the second request. This prevents
   // clients from accidentally creating duplicate commitments.
@@ -880,9 +880,9 @@ message TransferCounters {
   // Bytes that are copied to the data destination.
   int64 bytes_copied = 6;
 
-  // Objects that are failed to write to the data destination.
+  // Objects that failed to be written to the data destination.
   int64 objects_failed = 7;
 
-  // Bytes that are failed to write to the data destination.
+  // Bytes that failed to be written to the data destination.
   int64 bytes_failed = 8;
 }
