docs: bump rumdl to fix sentence-per-line for i.e., .e.g (#5805)

Author: davidhewitt

guide/src/building-and-distribution/multiple-python-versions.md

@@ -76,8 +76,7 @@ This `#[cfg]` marks code that will only be present on Python versions before (bu
 #[cfg(not(Py_LIMITED_API))]
 ```
 
-This `#[cfg]` marks code that is only available when building for the unlimited Python API (i.e.
-PyO3's `abi3` feature is not enabled).
+This `#[cfg]` marks code that is only available when building for the unlimited Python API (i.e. PyO3's `abi3` feature is not enabled).
 This might be useful if you want to ship your extension module as an `abi3` wheel and also allow users to compile it from source to make use of optimizations only possible with the unlimited API.
 
 ```text

guide/src/features.md

@@ -97,8 +97,7 @@ Disabling this feature enables faster builds for those users, as these dependenc
 This feature enables each `#[pyclass]` to have more than one `#[pymethods]` block.
 
 Most users should only need a single `#[pymethods]` per `#[pyclass]`.
-In addition, not all platforms (e.g.
-Wasm) are supported by `inventory`, which is used in the implementation of the feature.
+In addition, not all platforms (e.g. Wasm) are supported by `inventory`, which is used in the implementation of the feature.
 For this reason this feature is not enabled by default, meaning fewer dependencies and faster compilation for the majority of users.
 
 See [the `#[pyclass]` implementation details](class.md#implementation-details) for more information.

guide/src/function.md

@@ -81,8 +81,7 @@ It can take any combination of the following options:
     It is then possible to use the module in the function body.
     The first argument **must** be of type `&Bound<'_, PyModule>`, `Bound<'_, PyModule>`, or `Py<PyModule>`.
 
-    The following example creates a function `pyfunction_with_module` which returns the containing module's name (i.e.
-    `module_with_fn`):
+    The following example creates a function `pyfunction_with_module` which returns the containing module's name (i.e. `module_with_fn`):
 
     ```rust,no_run
     #[pyo3::pymodule]

guide/src/migration.md

@@ -2143,8 +2143,7 @@ If you need this functionality, you must enable the `multiple-pymethods` feature
 <details>
 <summary><small>Click to expand</small></summary>
 
-Some protocol (aka `__dunder__`) methods such as `__bytes__` and `__format__` have been possible to implement two ways in PyO3 for some time: via a `#[pyproto]` (e.g.
-`PyObjectProtocol` for the methods listed here), or by writing them directly in `#[pymethods]`.
+Some protocol (aka `__dunder__`) methods such as `__bytes__` and `__format__` have been possible to implement two ways in PyO3 for some time: via a `#[pyproto]` (e.g. `PyObjectProtocol` for the methods listed here), or by writing them directly in `#[pymethods]`.
 This is only true for a handful of the `#[pyproto]` methods (for technical reasons to do with the way PyO3 currently interacts with the Python C-API).
 
 In the interest of having only one way to do things, the `#[pyproto]` forms of these methods have been deprecated.