docs: [cloudkms] Minor formatting (#9794)

* docs: Minor formatting

PiperOrigin-RevId: 561417614

Source-Link: googleapis/googleapis@3d8c581

Source-Link: googleapis/googleapis-gen@67f16f3
Copy-Tag: eyJwIjoiamF2YS1rbXMvLk93bEJvdC55YW1sIiwiaCI6IjY3ZjE2ZjMxNjY2ZDg4ZWEyYWQ3OWNiMzgzZWU1MDY4NmU4MWJkOWEifQ==

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

java-kms/proto-google-cloud-kms-v1/src/main/java/com/google/cloud/kms/v1/CryptoKeyVersion.java

@@ -93,37 +93,37 @@ public static final com.google.protobuf.Descriptors.Descriptor getDescriptor() {
    * [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
    * [ENCRYPT_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ENCRYPT_DECRYPT].
    *
-   * Algorithms beginning with "RSA_SIGN_" are usable with
+   * Algorithms beginning with `RSA_SIGN_` are usable with
    * [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
    * [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
    *
-   * The fields in the name after "RSA_SIGN_" correspond to the following
+   * The fields in the name after `RSA_SIGN_` correspond to the following
    * parameters: padding algorithm, modulus bit length, and digest algorithm.
    *
    * For PSS, the salt length used is equal to the length of digest
    * algorithm. For example,
    * [RSA_SIGN_PSS_2048_SHA256][google.cloud.kms.v1.CryptoKeyVersion.CryptoKeyVersionAlgorithm.RSA_SIGN_PSS_2048_SHA256]
    * will use PSS with a salt length of 256 bits or 32 bytes.
    *
-   * Algorithms beginning with "RSA_DECRYPT_" are usable with
+   * Algorithms beginning with `RSA_DECRYPT_` are usable with
    * [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
    * [ASYMMETRIC_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_DECRYPT].
    *
-   * The fields in the name after "RSA_DECRYPT_" correspond to the following
+   * The fields in the name after `RSA_DECRYPT_` correspond to the following
    * parameters: padding algorithm, modulus bit length, and digest algorithm.
    *
-   * Algorithms beginning with "EC_SIGN_" are usable with
+   * Algorithms beginning with `EC_SIGN_` are usable with
    * [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
    * [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
    *
-   * The fields in the name after "EC_SIGN_" correspond to the following
+   * The fields in the name after `EC_SIGN_` correspond to the following
    * parameters: elliptic curve, digest algorithm.
    *
-   * Algorithms beginning with "HMAC_" are usable with
+   * Algorithms beginning with `HMAC_` are usable with
    * [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
    * [MAC][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.MAC].
    *
-   * The suffix following "HMAC_" corresponds to the hash algorithm being used
+   * The suffix following `HMAC_` corresponds to the hash algorithm being used
    * (eg. SHA256).
    *
    * For more information, see [Key purposes and algorithms]

java-kms/proto-google-cloud-kms-v1/src/main/proto/google/cloud/kms/v1/resources.proto

@@ -304,37 +304,37 @@ message CryptoKeyVersion {
   // [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
   // [ENCRYPT_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ENCRYPT_DECRYPT].
   //
-  // Algorithms beginning with "RSA_SIGN_" are usable with
+  // Algorithms beginning with `RSA_SIGN_` are usable with
   // [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
   // [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
   //
-  // The fields in the name after "RSA_SIGN_" correspond to the following
+  // The fields in the name after `RSA_SIGN_` correspond to the following
   // parameters: padding algorithm, modulus bit length, and digest algorithm.
   //
   // For PSS, the salt length used is equal to the length of digest
   // algorithm. For example,
   // [RSA_SIGN_PSS_2048_SHA256][google.cloud.kms.v1.CryptoKeyVersion.CryptoKeyVersionAlgorithm.RSA_SIGN_PSS_2048_SHA256]
   // will use PSS with a salt length of 256 bits or 32 bytes.
   //
-  // Algorithms beginning with "RSA_DECRYPT_" are usable with
+  // Algorithms beginning with `RSA_DECRYPT_` are usable with
   // [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
   // [ASYMMETRIC_DECRYPT][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_DECRYPT].
   //
-  // The fields in the name after "RSA_DECRYPT_" correspond to the following
+  // The fields in the name after `RSA_DECRYPT_` correspond to the following
   // parameters: padding algorithm, modulus bit length, and digest algorithm.
   //
-  // Algorithms beginning with "EC_SIGN_" are usable with
+  // Algorithms beginning with `EC_SIGN_` are usable with
   // [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
   // [ASYMMETRIC_SIGN][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.ASYMMETRIC_SIGN].
   //
-  // The fields in the name after "EC_SIGN_" correspond to the following
+  // The fields in the name after `EC_SIGN_` correspond to the following
   // parameters: elliptic curve, digest algorithm.
   //
-  // Algorithms beginning with "HMAC_" are usable with
+  // Algorithms beginning with `HMAC_` are usable with
   // [CryptoKey.purpose][google.cloud.kms.v1.CryptoKey.purpose]
   // [MAC][google.cloud.kms.v1.CryptoKey.CryptoKeyPurpose.MAC].
   //
-  // The suffix following "HMAC_" corresponds to the hash algorithm being used
+  // The suffix following `HMAC_` corresponds to the hash algorithm being used
   // (eg. SHA256).
   //
   // For more information, see [Key purposes and algorithms]