"Making subsystems exportable with their default lockfile" docs render funny

[huonw]

Describe the bug

The new docs for exporting tools https://www.pantsbuild.org/2.21/docs/writing-plugins/common-subsystem-tasks#making-subsystems-exportable-with-their-default-lockfile renders a bit funny. It looks like a list ends up nested within a :::note unintentionally?

pants/docs/docs/writing-plugins/common-subsystem-tasks.mdx

Lines 53 to 78 in 2505e54

	## Making subsystems exportable with their default lockfile
	:::note Support depends on language backend of the subsystem
	Only some language backends support `pants export`. These include the Python and JVM backends. Only tools which are themselves written to use a backend with this feature can be exported. For example, a Python-based tool which operates on a different language is exportable.
	1. Make the subsystem a subclass of `ExportableTool`
	:::note Language backends may have done this in their Tool base class. For example, the Python backend with `PythonToolRequirementsBase` and JVM with `JvmToolBase` are already subclasses.
	```python
	from pants.backend.python.subsystems.python_tool_base import PythonToolBase
	from pants.core.goals.resolves import ExportableTool
	class FortranLint(PythonToolBase, ExportableTool):
	...
	```
	2. Register your class with a `UnionRule` with `ExportableTool`
	```python
	def rules():
	return [
	UnionRule(ExportableTool, FortranLint)
	]
	```

I think :::note admonitions require a ::: on its own line to close them: https://docusaurus.io/docs/markdown-features/admonitions

Pants version

2.21

OS
N/A

Additional info
Add any other information about the problem here, such as attachments or links to gists, if relevant.