fix rumdl formatting

Author: davidhewitt

guide/src/class.md

@@ -1312,7 +1312,7 @@ Python::attach(|py| {
 # .unwrap();
 ```
 
-WARNING: `Py::new` and `.into_pyobject` are currently inconsistent. Note how the constructed value is _not_ an instance of the specific variant. For this reason, constructing values is only recommended using `.into_pyobject`.
+WARNING: `Py::new` and `.into_pyobject` are currently inconsistent. Note how the constructed value is *not* an instance of the specific variant. For this reason, constructing values is only recommended using `.into_pyobject`.
 
 ```rust
 # use pyo3::prelude::*;

guide/src/class/protocols.md

@@ -78,7 +78,7 @@ given signatures should be interpreted as follows:
 
     The implementations of Python's "rich comparison" operators `<`, `<=`, `==`, `!=`, `>` and `>=` respectively.
 
-    _Note that implementing any of these methods will cause Python not to generate a default `__hash__` implementation, so consider also implementing `__hash__`._
+    *Note that implementing any of these methods will cause Python not to generate a default XXXXXXXXXX implementation, so consider also implementing XXXXXXXXXX.*
     <details>
     <summary>Return type</summary>
     The return type will normally be `bool` or `PyResult<bool>`, however any Python object can be returned.
@@ -90,9 +90,9 @@ given signatures should be interpreted as follows:
     The `CompareOp` argument indicates the comparison operation being performed. You can use
     [`CompareOp::matches`] to adapt a Rust `std::cmp::Ordering` result to the requested comparison.
 
-    _This method cannot be implemented in combination with any of `__lt__`, `__le__`, `__eq__`, `__ne__`, `__gt__`, or `__ge__`._
+    *This method cannot be implemented in combination with any of XXXXXXXX, XXXXXXXX, XXXXXXXX, XXXXXXXX, XXXXXXXX, or XXXXXXXX.*
 
-    _Note that implementing `__richcmp__` will cause Python not to generate a default `__hash__` implementation, so consider implementing `__hash__` when implementing `__richcmp__`._
+    *Note that implementing XXXXXXXXXXXXX will cause Python not to generate a default XXXXXXXXXX implementation, so consider implementing XXXXXXXXXX when implementing XXXXXXXXXXXXX.*
     <details>
     <summary>Return type</summary>
     The return type will normally be `PyResult<bool>`, but any Python object can be returned.

pyproject.toml

@@ -33,7 +33,9 @@ disable = [
     # TODO: what to do about inline HTML, probably allow?
     "MD033",
     # TODO: {{#PYO3_DOCS_URL}} placeholder confuses rumdl, change syntax perhaps?
-    "MD051"
+    "MD051",
+    # Disabled on release-0.27 branch
+    "MD059",
 ]
 
 exclude = [