fix docs for MDX3

[Arhell]

What type of PR is this?

Add one of the following kinds:

/kind bug
/kind cleanup
/kind documentation
/kind feature

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign poor12, rainbowmango for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• docs/OWNERS
• i18n/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Arhell]

@RainbowMango

[RainbowMango]

I wonder do we need a guide for people to write docs with MDX3 compliant?

[Arhell]

I think yes, if we want to update to version 3.
As for me, you just need to wrap these variables {{ POD_NAME }} in something ***{{ POD_NAME }}*** for example or other ``` characters.

And it would be good to do something about this #565 (comment)
Because it could be a problem.

[samzong]

Perhaps we should integrate a syntax detection command into git commit, allowing users to identify issues promptly and receive appropriate solutions, thereby preventing collective confusion.

MDX3 appears to be more stringent than Markdown, and it's unclear whether this is advantageous.

[windsonsea]

`` seems more common in markdown like:

• Example 1: {{ POD_NAME }}

• Example 2:

  CLUSTER_NAME=<member_cluster_name>
  HOST_IP=<member_cluster_entry_ip>
  PORT=<member_cluster_entry_port>
  KUBECONFIG=<member_cluster_kubeconfig>
  

[Arhell]

Merge?

[Arhell]

@windsonsea #575 (comment) yes. There are a lot of such files, I do a little at a time.