I noticed some strange descriptions for actions in our api schema when viewing it as json. I'm hitting the /pulp/api/v3/docs/api.json endpoint and seeing: <pre> <!-- User-facing documentation, rendered as html-->\nFileRemote represents an external source of <a href=\"#operation/content_file_files_list\">File\nContent</a>. The target url of a FileRemote must contain a file manifest, which contains the\nmetadata for all files at the source. </pre> I wonder if don't think we should avoid be including html in fields as our api schema since it can be rendered in many different forms (e.g. json).