Tweak docs

Author: Tinche

HISTORY.md

@@ -8,6 +8,8 @@
 - **Potentially breaking**: {py:func}`cattrs.gen.make_dict_structure_fn` and {py:func}`cattrs.gen.typeddicts.make_dict_structure_fn` will use the values for the `detailed_validation` and `forbid_extra_keys` parameters from the given converter by default now.
   If you're using these functions directly, the old behavior can be restored by passing in the desired values directly.
   ([#410](https://github.com/python-attrs/cattrs/issues/410) [#411](https://github.com/python-attrs/cattrs/pull/411))
+- Introduce the `use_class_methods` strategy. Learn more [here](https://catt.rs/en/latest/strategies.html#using-class-specific-structure-and-unstructure-methods).
+  ([#405](https://github.com/python-attrs/cattrs/pull/405))
 - The `omit` parameter of {py:func}`cattrs.override` is now of type `bool | None` (from `bool`).
   `None` is the new default and means to apply default _cattrs_ handling to the attribute, which is to omit the attribute if it's marked as `init=False`, and keep it otherwise.
 - Fix {py:func}`format_exception() <cattrs.v.format_exception>` parameter working for recursive calls to {py:func}`transform_error <cattrs.transform_error>`.
@@ -39,7 +41,6 @@
 - Add support for `date` to preconfigured converters.
   ([#420](https://github.com/python-attrs/cattrs/pull/420))
 
-
 ## 23.1.2 (2023-06-02)
 
 - Improve `typing_extensions` version bound. ([#372](https://github.com/python-attrs/cattrs/issues/372))

README.md

@@ -149,6 +149,7 @@ _cattrs_ is based on a few fundamental design decisions.
 
 - Un/structuring rules are separate from the models.
   This allows models to have a one-to-many relationship with un/structuring rules, and to create un/structuring rules for models which you do not own and you cannot change.
+  (_cattrs_ can be configured to use un/structuring rules from models using the [`use_class_methods` strategy](https://catt.rs/en/latest/strategies.html#using-class-specific-structure-and-unstructure-methods).)
 - Invent as little as possible; reuse existing ordinary Python instead.
   For example, _cattrs_ did not have a custom exception type to group exceptions until the sanctioned Python [`exceptiongroups`](https://docs.python.org/3/library/exceptions.html#ExceptionGroup).
   A side-effect of this design decision is that, in a lot of cases, when you're solving _cattrs_ problems you're actually learning Python instead of learning _cattrs_.
@@ -163,6 +164,7 @@ A foolish consistency is the hobgoblin of little minds so these decisions can an
 - [Why I use attrs instead of pydantic](https://threeofwands.com/why-i-use-attrs-instead-of-pydantic/)
 - [cattrs I: un/structuring speed](https://threeofwands.com/why-cattrs-is-so-fast/)
 - [Python has a macro language - it's Python (PyCon IT 2022)](https://www.youtube.com/watch?v=UYRSixikUTo)
+- [Intro to cattrs 23.1](https://threeofwands.com/intro-to-cattrs-23-1-0/)
 
 ## Credits
 

docs/strategies.md

@@ -221,6 +221,7 @@ Child2(a=1, b=1)
 ```
 
 Other customizations available see are (see {py:func}`include_subclasses()<cattrs.strategies.include_subclasses>`):
+
 - The exact list of subclasses that should participate to the union with the `subclasses` argument.
 - Attribute overrides that permit the customization of attributes un/structuring like renaming an attribute.
 
@@ -259,13 +260,12 @@ Child(a=1, b='foo')
 
 ```
 
-
-
-### Using Class-Specific Structure and Unstructure Methods
+## Using Class-Specific Structure and Unstructure Methods
 
 _Found at {py:func}`cattrs.strategies.use_class_methods`._
 
-The following strategy can be applied for both structuring and unstructuring (also simultaneously).
+This strategy allows for un/structuring logic on the models themselves.
+It can be applied for both structuring and unstructuring (also simultaneously).
 
 If a class requires special handling for (un)structuring, you can add a dedicated (un)structuring
 method:
@@ -295,11 +295,11 @@ MyClass(a=43)
 {'c': 41}
 ```
 
-Any class without a `_structure` or `_unstructure` method will use the default strategy for
-structuring or unstructuring, respectively. Feel free to use other names.
+Any class without a `_structure` or `_unstructure` method will use the default strategy for structuring or unstructuring, respectively.
+Feel free to use other names.
+The stategy can be applied multiple times (with different method names).
 
-If you want to (un)structured nested objects, just append a converter parameter
-to your (un)structuring methods and you will receive the converter there:
+If you want to (un)structured nested objects, just append a converter parameter to your (un)structuring methods and you will receive the converter there:
 
 ```{doctest} class_methods