Change RST code formatting markup to Markdown

data/api/application-service/definitions/protocol.yaml

@@ -43,9 +43,9 @@ properties:
   field_types:
     title: Field Types
     description: |-
-      The type definitions for the fields defined in the ``user_fields`` and 
-      ``location_fields``. Each entry in those arrays MUST have an entry here. The
-      ``string`` key for this object is field name itself.
+      The type definitions for the fields defined in the `user_fields` and
+      `location_fields`. Each entry in those arrays MUST have an entry here. The
+      `string` key for this object is field name itself.
 
       May be an empty object if no fields are defined.
     type: object
@@ -101,7 +101,7 @@ properties:
           example: "mxc://example.org/JkLmNoPq"
         fields:
           type: object
-          description: Preset values for ``fields`` the client may use to search by.
+          description: Preset values for `fields` the client may use to search by.
           example: {
             "network": "freenode"
           }

data/api/application-service/definitions/security.yaml

@@ -13,6 +13,6 @@
 # limitations under the License.
 homeserverAccessToken:
   type: apiKey
-  description: The ``hs_token`` provided by the application service's registration.
+  description: The `hs_token` provided by the application service's registration.
   name: access_token
   in: query

data/api/application-service/query_room.yaml

@@ -34,7 +34,7 @@ paths:
       description: |-
         This endpoint is invoked by the homeserver on an application service to query
         the existence of a given room alias. The homeserver will only query room
-        aliases inside the application service's ``aliases`` namespace. The
+        aliases inside the application service's `aliases` namespace. The
         homeserver will send this request when it receives a request to join a
         room alias within the application service's namespace.
       operationId: queryRoomByAlias

data/api/application-service/query_user.yaml

@@ -34,7 +34,7 @@ paths:
       description: |-
         This endpoint is invoked by the homeserver on an application service to query
         the existence of a given user ID. The homeserver will only query user IDs
-        inside the application service's ``users`` namespace. The homeserver will
+        inside the application service's `users` namespace. The homeserver will
         send this request when it receives an event for an unknown user ID in
         the application service's namespace, such as a room invite.
       operationId: queryUserById

data/api/application-service/transactions.yaml

@@ -34,7 +34,7 @@ paths:
         (or batch of events) to the application service.
 
         Note that the application service should distinguish state events
-        from message events via the presence of a ``state_key``, rather than
+        from message events via the presence of a `state_key`, rather than
         via the event type.
       operationId: sendTransaction
       security: