chore(dev): fix markdown lint failures

rfcs/2020-03-06-1999-api-extensions-for-lua-transform.md

@@ -471,12 +471,12 @@ Here `event` is an encoded event to be produced by the transform, and `lane` is
 
 > An emitting function is called from a transform component called `example_transform` with `lane` parameter set to `example_lane`. Then the downstream `console` sink have to be defined as the following to be able to read the emitted event:
 >
->    ```toml
->    [sinks.example_console]
->      type = "console"
->      inputs = ["example_transform.example_lane"] # would output the event from `example_lane`
->      encoding.codec = "text"
->    ```
+> ```toml
+> [sinks.example_console]
+> type = "console"
+> inputs = ["example_transform.example_lane"] # would output the event from `example_lane`
+> encoding.codec = "text"
+>  ```
 >
 > Other components connected to the same transform, but with different lanes names or without lane names at all would not receive any event.
 

website/content/en/highlights/2022-03-22-0-21-0-upgrade-guide.md

@@ -238,8 +238,8 @@ The new AWS SDK lacks support for certain authentication configuration:
 
 - Vector now only supports IMDSv2 for authentication. If you were previously using IMDSv1, you will need to configure
   the host to allow IMDSv2. For EKS, this likely means increasing the metadata token response hop limit to 2 (see
-  [Amazon EKS now supports EC2 Instance Metadata Service v2
-  ](https://aws.amazon.com/about-aws/whats-new/2020/08/amazon-eks-supports-ec2-instance-metadata-service-v2/). We are
+  [Amazon EKS now supports EC2 Instance Metadata Service v2](https://aws.amazon.com/about-aws/whats-new/2020/08/amazon-eks-supports-ec2-instance-metadata-service-v2/).
+  We are
   discussing the possibility of re-adding support for IMDSv1 in
   [#12376](https://github.com/vectordotdev/vector/issues/12376).
 - Vector AWS components' `auth.credential_file` option was removed as the new [SDK does not yet support it