Tweak docs

HISTORY.md

@@ -20,8 +20,8 @@
   ([#350](https://github.com/python-attrs/cattrs/issues/350) [#353](https://github.com/python-attrs/cattrs/pull/353))
 - Subclasses structuring and unstructuring is now supported via a custom `include_subclasses` strategy.
   ([#312](https://github.com/python-attrs/cattrs/pull/312))
-- Add unstructuring and structuring support to `deque` in standard lib.
-  ([#355](https://github.com/python-attrs/cattrs/issues/355))
+- Add unstructuring and structuring support for the standard library `deque`.
+  ([#355](https://github.com/python-attrs/cattrs/pull/355))
 
 ## 22.2.0 (2022-10-03)
 

docs/strategies.md

@@ -169,7 +169,7 @@ Without the application of the strategy, in both unstructure and structure opera
 ```{note}
 The handling of subclasses is an opt-in feature for two main reasons:
 - Performance. While small and probably negligeable in most cases the subclass handling incurs more function calls and has a performance impact. 
-- Customization. The specific handling of subclasses can be different from one situation to the other. In particular there is not apparent universal good defaults for disambiguating the union type. Consequently The decision is left to the `cattrs` user.
+- Customization. The specific handling of subclasses can be different from one situation to the other. In particular there is not apparent universal good defaults for disambiguating the union type. Consequently the decision is left to the user.
 ```
 
 ```{warning}
@@ -249,4 +249,4 @@ Here is an example involving both customizations:
 
 >>> converter.structure({'a': 1, 'c': 'foo'}, Parent)
 Child(a=1, b='foo')
-```
+```