Update MDX guide and fix some GP issues (#3966)

This PR fixes some files that were causing problems when they were sent
to translate & updates the MDX guide to reflect some constrains when
using definition tooltips and setting the markdown metadata.

---------

Co-authored-by: Eric Arellano <[email protected]>

Author: arnaucasau

docs/guides/visualize-results.ipynb

@@ -35,7 +35,7 @@
    "id": "e8d0138c-fd97-49c2-88a5-1929a5a09258",
    "metadata": {},
    "source": [
-    "## Plot histogram <a name='histogram'></a>\n",
+    "## Plot histogram\n",
     "\n",
     "The `plot_histogram` function visualizes the result of sampling a quantum circuit on a QPU.\n",
     "\n",

docs/migration-guides/migrate-classic-rest-api.mdx

@@ -106,7 +106,7 @@ For the whole schema, see the [Qiskit Runtime API.](https://quantum.cloud.ibm.co
 | --------   | ------   | ------- |
 | GET | `/facade/v1/jobs/tags` | `/v1/tags` |
 | GET | `/facade/v1/jobs/\{id\}/type` | **N/A** |
-| GET | `/jobs* <br/> `/jobs/\{id\}` <br/> `/jobs/\{id\}/metrics`  | `/v1/jobs` <br/> `/v1/jobs/\{id\}` <br/> `/v1/jobs/\{id\}/metrics` |
+| GET | `/jobs*` <br/> `/jobs/\{id\}` <br/> `/jobs/\{id\}/metrics`  | `/v1/jobs` <br/> `/v1/jobs/\{id\}` <br/> `/v1/jobs/\{id\}/metrics` |
 | GET | `/jobs/\{id\}/interim_results` <br/> `/jobs/\{id\}/transpiled_circuits` <br/> `/jobs/\{id\}/logs`  | `/v1/jobs/\{id\}/interim_results` <br/> `/v1/jobs/\{id\}/transpiled_circuits` <br/> `/v1/jobs/\{id\}/logs` |
 | POST | `/jobs/\{id\}/cancel` | `/v1/jobs/\{id\}/cancel` |
 | PUT | `/jobs/\{id\}/tags` | `/v1/jobs/\{id\}/tags` |

learning/courses/quantum-safe-cryptography/quantum-safe-cryptography.ipynb

@@ -56,7 +56,7 @@
    "source": [
     "## Quantum algorithms and impacts to cryptography\n",
     "\n",
-    "| Quantum Algorithm | Functionality      | <DefinitionTooltip definition=\"As defined by the [NIST](https://csrc.nist.gov/glossary/term/security_strength): *A number characterizing the amount of work that is expected to suffice to “defeat” an implemented cryptographic mechanism (for example, by compromising its functionality and/or circumventing the protection that its use was intended to facilitate). Security strength is often expressed in bits. If the security strength of a particular implementation of a cryptographic mechanism is s bits, it is expected that the equivalent of (roughly) 2<sup>s</sup> basic operations of some sort will be sufficient to defeat it in some way.*\">Security Strength</DefinitionTooltip> ($n$ = number of bits) | Impacted Cryptographic Protocols                 | Mitigation             |\n",
+    "| Quantum Algorithm | Functionality      | <DefinitionTooltip definition=\"As defined by the [NIST](https://csrc.nist.gov/glossary/term/security_strength): *A number characterizing the amount of work that is expected to suffice to defeat an implemented cryptographic mechanism (for example, by compromising its functionality and/or circumventing the protection that its use was intended to facilitate). Security strength is often expressed in bits. If the security strength of a particular implementation of a cryptographic mechanism is s bits, it is expected that the equivalent of (roughly) 2<sup>s</sup> basic operations of some sort will be sufficient to defeat it in some way.*\">Security Strength</DefinitionTooltip> ($n$ = number of bits) | Impacted Cryptographic Protocols                 | Mitigation             |\n",
     "|-------------------|--------------------|------------------------------------------------------|--------------------------------------------------|------------------------|\n",
     "| Shor              | factoring          | $poly(n)$                                            | RSA                                              | Migrate to QSC         |\n",
     "| Shor              | discrete logarithm | $poly(n)$                                            | Diffie-Hellman, DSA, Elliptic Curve Cryptography | Migrate to QSC         |\n",

mdx-guide.md

@@ -56,6 +56,8 @@ In Jupyter notebooks, set `title` and `description` in the `metadata` section fo
 }
 ```
 
+Avoid using hyphens, colons, semicolons, backticks, and pipes when writing the `title` and `description`. These characters might be used differently in other languages, and their use might complicate the translation process. Our translation tooling often replaces them with other symbols that could change their meaning or even break the page.
+
 ## Links
 
 Internal URLs referring to other docs pages should start with `/docs` and not include the file extension. For example:
@@ -219,7 +221,10 @@ To use a `DefinitionTooltip`, use the following syntax:
 
 For full list of props, please check [here](https://react.carbondesignsystem.com/?path=/docs/components-definitiontooltip--playground#component-api).
 
-Warning: do not use LaTeX/math expressions in the same paragraph as a definition tooltip because it will break the styling. Use a new line to separate out the two into separate paragraphs.
+Caveats:
+
+1. Do not use any interactive content (e.g. links) with the `definition` prop or inside the tags. If you use such content, it will not be available to users of screen reader software.
+2. Do not use single and double quotes in the `definition` prop. Even if they are escaped, they cause problems when translating the files.
 
 ### Tabs