Fix linter issues

docs/pages/choose-an-edition/migrate-to-cloud.mdx

@@ -31,10 +31,10 @@ Enterprise cluster:
 - An existing Teleport Enterprise (self-hosted) cluster.
 - The `tsh` and `tctl` client tools. This guide assumes that you are using
   `tctl` to manage dynamic resources, but it is also possible to use [Teleport
-  Terraform provider](./management/dynamic-resources/terraform-provider.mdx) and
+  Terraform provider](../management/dynamic-resources/terraform-provider.mdx) and
   [Kubernetes
-  operator](./management/dynamic-resources/teleport-operator-standalone.mdx), in
-  addition to custom scripts that use the [Teleport API](./api/introduction.mdx)
+  operator](../management/dynamic-resources/teleport-operator-standalone.mdx), in
+  addition to custom scripts that use the [Teleport API](../api/introduction.mdx)
   to manage the Teleport Auth Service backend.
 - An account with no trusted clusters enrolled. Trusted clusters are not
   supported in cloud-hosted Teleport Enterprise accounts. You will not be able
@@ -109,7 +109,7 @@ cluster uses a separate Auth Service backend from your cloud-hosted cluster, you
 must retrieve the resources on the first backend, then re-apply them against the
 second backend.
 
-Review the [dynamic resources](https://goteleport.com/docs/reference/resources/)
+Review the [dynamic resources](../reference/resources.mdx)
 list to see if any other resources need to be migrated. Some common dynamic
 resources includes:
 
@@ -173,7 +173,7 @@ To migrate Teleport agents:
 
 1. For each agent and Machine ID bot, obtain a valid join token. We recommend
    using a [delegated join
-   method](https://goteleport.com/docs/reference/join-methods/#delegated-join-methods).
+   method](../reference/join-methods.mdx#delegated-join-methods).
 
 1. If using ephemeral tokens, ensure you specify the appropriate token type to
    match the Teleport services. Token types can include `node`, `app`, `kube`,
@@ -206,7 +206,7 @@ To migrate Teleport agents:
       proxy_server: example.teleport.sh:443
    ```
 
-   If your agent configuration does _not_ include a `teleport.proxy_server`
+   If your agent configuration does *not* include a `teleport.proxy_server`
    field, and instead has a `teleport.auth_server` or `teleport.auth_servers`
    field, we recommend migrating your configuration to `version: v3` and using
    `teleport.proxy_server`. 
@@ -257,7 +257,7 @@ In general, you can migrate a Machine ID bot using the following steps:
 1. Restart `tbot`.
 
 To learn how to restart and configure a Machine ID bot in your infrastructure,
-read the [full documentation](./machine-id/deployment.mdx) on deploying a
+read the [full documentation](../machine-id/deployment.mdx) on deploying a
 Machine ID Bot.
 
 ### Access Request plugins and the Event Handler
@@ -279,8 +279,8 @@ In general, you can migrate Teleport plugins using the following steps:
 
 For specific plugins running in your infrastructure, read the full documentation
 on:
-- [Access Request plugins](./access-controls/access-request-plugins.mdx)
-- The [Teleport Event Handler](./management/export-audit-events.mdx)
+- [Access Request plugins](../access-controls/access-request-plugins/index.mdx)
+- The [Teleport Event Handler](../management/export-audit-events.mdx)
 
 ## Step 4/4. Verify end user access and performance