Add backticks for field name in deprecation_message example (#9657)

GoogleCloudPlatform · Dec 18, 2023 · 31d4404 · 31d4404
1 parent b0dc7d3
commit 31d4404
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/content/develop/make-a-breaking-change.md b/docs/content/develop/make-a-breaking-change.md
@@ -93,7 +93,7 @@ Set `deprecation_message` on the field. For example:
   name: 'apiFieldName'
   description: |
     MULTILINE_FIELD_DESCRIPTION
-  deprecation_message: api_field_name is deprecated and will be removed in a future major release. Use other_field_name instead.
+  deprecation_message: "`api_field_name` is deprecated and will be removed in a future major release. Use `other_field_name` instead."
 ```
 
 Replace the second sentence with an appropriate short description of the replacement path and/or the reason for
@@ -107,7 +107,7 @@ The deprecation message will automatically show up in the resource documentation
    ```go
    "api_field_name": {
       Type:       schema.String,
-      Deprecated: "api_field_name is deprecated and will be removed in a future major release. Use other_field_name instead.",
+      Deprecated: "`api_field_name` is deprecated and will be removed in a future major release. Use `other_field_name` instead.",
       ...
    }
    ```