Fix mtls reference

daprdocs/content/en/concepts/security-concept.md

@@ -42,7 +42,7 @@ Dapr also supports strong identities when deployed on Kubernetes, relying on a p
 By default, a workload cert is valid for 24 hours and the clock skew is set to 15 minutes.
 
 Mutual TLS can be turned off/on by editing the default configuration that is deployed with Dapr via the `spec.mtls.enabled` field.
-This can be done for both Kubernetes and self hosted modes. Details for how to do this can be found [here]({{< ref mtls.md >}}).
+This can be done for both Kubernetes and self hosted modes. Details for how to do this can be found [here]({{< ref mtls >}}).
 
 ### mTLS self hosted
 The diagram below shows how the Sentry system service issues certificates for applications based on the root/issuer certificate that is provided by an operator or generated by the Sentry service as stored in a file

daprdocs/content/en/operations/configuration/configuration-overview.md

@@ -175,7 +175,7 @@ A Dapr control plane configuration can configure the following settings:
 | allowedClockSkew | string | The extra time to give for certificate expiry based on possible clock skew on a machine. Default is 15 minutes.
 | workloadCertTTL  | string | Time a certificate is valid for. Default is 24 hours
 
-See the [Mutual TLS]({{< ref "mtls.md" >}}) HowTo and [security concepts]({{< ref "security-concept.md" >}}) for more information.
+See the [Mutual TLS]({{< ref "mtls" >}}) HowTo and [security concepts]({{< ref "security-concept.md" >}}) for more information.
 
 ### Example control plane configuration
 

daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md

@@ -256,7 +256,7 @@ Properly configured, Dapr not only be secured with regards to it's control plane
 
 It is recommended that a production-ready deployment includes the following settings:
 
-1. Mutual Authentication (mTLS) should be enabled. Note that Dapr has mTLS on by default. For details on how to bring your own certificates, see [here]({{< ref "mtls.md#bringing-your-own-certificates" >}})
+1. Mutual Authentication (mTLS) should be enabled. Note that Dapr has mTLS on by default. For details on how to bring your own certificates, see [here]({{< ref "mtls#bringing-your-own-certificates" >}})
 
 2. Dapr API authentication is enabled (this is the between your application and the Dapr sidecar). To secure the Dapr API from unauthorized access, it is recommended to enable Dapr's token based auth. See [here]({{< ref "api-token.md" >}}) for details
 

daprdocs/content/en/reference/cli/cli-overview.md

@@ -59,7 +59,7 @@ You can learn more about each Dapr command from the links below.
  - [`dapr invoke`]({{< ref dapr-invoke.md >}})
  - [`dapr list`]({{< ref dapr-list.md >}})
  - [`dapr logs`]({{< ref dapr-logs.md >}})
- - [`dapr mtls`]({{< ref dapr-mtls.md >}})
+ - [`dapr mtls`]({{< ref dapr-mtls >}})
  - [`dapr publish`]({{< ref dapr-publish.md >}})
  - [`dapr run`]({{< ref dapr-run.md >}})
  - [`dapr status`]({{< ref dapr-status.md >}})