code.rb in google-cloud-container-v1beta1-0.15.0

- old
+ new

@@ -25,11 +25,11 @@
     # Sometimes multiple error codes may apply.  Services should return
     # the most specific error code that applies.  For example, prefer
     # `OUT_OF_RANGE` over `FAILED_PRECONDITION` if both codes apply.
     # Similarly prefer `NOT_FOUND` or `ALREADY_EXISTS` over `FAILED_PRECONDITION`.
     module Code
-      # Not an error; returned on success
+      # Not an error; returned on success.
       #
       # HTTP Mapping: 200 OK
       OK = 0
 
       # The operation was cancelled, typically by the caller.
@@ -64,11 +64,11 @@
       DEADLINE_EXCEEDED = 4
 
       # 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.
       #
       # HTTP Mapping: 404 Not Found
@@ -110,14 +110,14 @@
       # a non-directory, etc.
       #
       # 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.
       #
       # HTTP Mapping: 400 Bad Request