Update contrib/libs/googleapis-common-protos to 1.58.0

1 files changed, 7 insertions, 7 deletions

diff --git a/contrib/libs/googleapis-common-protos/google/rpc/code.proto b/contrib/libs/googleapis-common-protos/google/rpc/code.proto
index 98ae0ac18f..7c810af40f 100644
--- a/contrib/libs/googleapis-common-protos/google/rpc/code.proto
+++ b/contrib/libs/googleapis-common-protos/google/rpc/code.proto
@@ -1,4 +1,4 @@
-// Copyright 2020 Google LLC
+// Copyright 2022 Google LLC
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
@@ -30,7 +30,7 @@ option objc_class_prefix = "RPC";
 // `OUT_OF_RANGE` over `FAILED_PRECONDITION` if both codes apply.
 // Similarly prefer `NOT_FOUND` or `ALREADY_EXISTS` over `FAILED_PRECONDITION`.
 enum Code {
-  // Not an error; returned on success
+  // Not an error; returned on success.
   //
   // HTTP Mapping: 200 OK
   OK = 0;
@@ -69,7 +69,7 @@ enum Code {
   // Some requested entity (e.g., file or directory) was not found.
   //
   // Note to server developers: if a request is denied for an entire class
-  // of users, such as gradual feature rollout or undocumented whitelist,
+  // of users, such as gradual feature rollout or undocumented allowlist,
   // `NOT_FOUND` may be used. If a request is denied for some users within
   // a class of users, such as user-based access control, `PERMISSION_DENIED`
   // must be used.
@@ -115,11 +115,11 @@ enum Code {
   // Service implementors can use the following guidelines to decide
   // between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`:
   //  (a) Use `UNAVAILABLE` if the client can retry just the failing call.
-  //  (b) Use `ABORTED` if the client should retry at a higher level
-  //      (e.g., when a client-specified test-and-set fails, indicating the
-  //      client should restart a read-modify-write sequence).
+  //  (b) Use `ABORTED` if the client should retry at a higher level. For
+  //      example, when a client-specified test-and-set fails, indicating the
+  //      client should restart a read-modify-write sequence.
   //  (c) Use `FAILED_PRECONDITION` if the client should not retry until
-  //      the system state has been explicitly fixed.  E.g., if an "rmdir"
+  //      the system state has been explicitly fixed. For example, if an "rmdir"
   //      fails because the directory is non-empty, `FAILED_PRECONDITION`
   //      should be returned since the client should not retry unless
   //      the files are deleted from the directory.