docs: fix mmds doc linter errors
@@ -41,7 +41,7 @@ desired data store structure and contents. Here's a JSON example:
Queries from the guest (more on them a bit later) will be applied to this
structure. For example, a `GET` request for
-**http://169.254.169.254/latest/meta-data/ami-id** will return a response body
+`http://169.254.169.254/latest/meta-data/ami-id` will return a response body
consisting of *ami-12345678*. The MMDS contents can be updated either via a
subsequent `PUT` (that replaces them entirely), or using `PATCH` requests,
which feed the JSON body into the merge functionality exposed by the
@@ -58,7 +58,7 @@ bottleneck first, which means any API resource may have this potential issue.
For this example, the guest expects to find some sort of credentials (say, a
secret access key) by issuing a `GET` request to
-*http://169.254.169.254/latest/meta-data/credentials/secret-key*. Most similar
+`http://169.254.169.254/latest/meta-data/credentials/secret-key`. Most similar
use cases will encompass the following sequence of steps:
1. Some agent running on the host sends a `PUT` request with the initial
