Format default status as code snippet

Co-authored-by: R. Miles McCain <[email protected]>

docs/content/docs/Technical/api.md

@@ -200,7 +200,7 @@ requests.post(
 
 It also has many optional parameters:
 - Any attribute, both core and custom. See below for more information on accessing attributes' API identifiers.
-- `status`, the incident's status. By default, the incident will be created as "To Do". If you include this field, you can set the incident to one of: `"To Do"`, `"In Progress"`, `"Ready for Review"`, `"Help Needed"`, `"Completed"`, or "`Canceled"`. 
+- `status`, the incident's status. By default, the incident will be created as `"To Do"`. If you include this field, you can set the incident to one of: `"To Do"`, `"In Progress"`, `"Ready for Review"`, `"Help Needed"`, `"Completed"`, or "`Canceled"`. 
 - `restrictions`, an array of the incident's restrictions. If you include this field, you can set the incident to one or both of `["Hidden", "Frozen"]`.
 - `tags`, an array of the incident's tags. If you include a value not yet present in the project, that tag will be created and applied to the incident.
 - `urls`, which should contain a list of urls to be archived as distinct pieces of source material. Unlike the other fields listed here, validation of URLs fails silently: if an invalid URL is included in this array, Atlos will create the incident without the relevant piece of source material. For more granular control over source material metadata, we recommend using the [source material creation endpoint](#create-a-new-piece-of-source-material) and the [source material metadata update endpoint](#set-source-material-metadata).