Automated build docs: 2025-04-11 04:51:29

Author: asana-push-openapi-spec[bot]

defs/asana_oas.yaml

@@ -2144,7 +2144,7 @@ components:
                 $ref: '#/components/schemas/EnumOption'
             precision:
               description: >-
-                Only relevant for custom fields of type ‘Number’. This field
+                Only relevant for custom fields of type `Number`. This field
                 dictates the number of places after the decimal to round to, i.e.
                 0 is integer values, 1 rounds to the nearest tenth, and so on.
                 Must be between 0 and 6, inclusive.
@@ -2858,7 +2858,7 @@ components:
           example: true
         color:
           description: >-
-            The color of the enum option. Defaults to ‘none’.
+            The color of the enum option. Defaults to `none`.
           type: string
           example: blue
     EnumOptionBase:
@@ -2935,7 +2935,7 @@ components:
           description: >-
             *500 errors only*. A unique error phrase which can be used
             when contacting developer support to help identify the exact
-            occurrence of the problem in Asana’s logs.
+            occurrence of the problem in Asana's logs.
           example: 6 sad squid snuggle softly
     ErrorResponse:
       description: |-
@@ -2965,7 +2965,7 @@ components:
 
         The event may be triggered by a different `user` than the
         subscriber. For example, if user A subscribes to a task and user B
-        modified it, the event’s user will be user B. Note: Some events
+        modified it, the event's user will be user B. Note: Some events
         are generated by the system, and will have `null` as the user. API
         consumers should make sure to handle this case.