Improvements and typo fixes in the readme

Author: hamdanal

README.md

@@ -53,7 +53,7 @@ parser = argparse.ArgumentParser(..., formatter_class=RichHelpFormatter)
 ...
 ```
 
-*rich-argparse* defines equivalents to argparse's [built-in formatters](
+*rich-argparse* defines equivalents to all argparse's [built-in formatters](
 https://docs.python.org/3/library/argparse.html#formatter-class):
 
 | `rich_argparse` formatter | equivalent in `argparse` |
@@ -128,8 +128,8 @@ parser = argparse.ArgumentParser(..., formatter_class=RichHelpFormatter)
 ### Colors in the `usage`
 
 The usage **generated by the formatter** is colored using the `argparse.args` and `argparse.metavar`
-styles. If you use a custom `usage` message in the parser, it will treated as "plain text" and will
-**not** be colored by default. You can enable colors in user defined usage message through
+styles. If you use a custom `usage` message in the parser, it will be treated as "plain text" and
+will **not** be colored by default. You can enable colors in user defined usage message through
 [console markup](https://rich.readthedocs.io/en/stable/markup.html) by setting
 `RichHelpFormatter.usage_markup = True`. If you enable this option, make sure to [escape](
 https://rich.readthedocs.io/en/stable/markup.html#escaping) any square brackets in the usage text.
@@ -151,7 +151,7 @@ and epilog.
 
 You can use any rich renderable in the descriptions and epilog. This includes all built-in rich
 renderables like `Table` and `Markdown` and any custom renderables defined using the
-[Console Protcol](https://rich.readthedocs.io/en/stable/protocol.html#console-protocol).
+[Console Protocol](https://rich.readthedocs.io/en/stable/protocol.html#console-protocol).
 
 ```python
 import argparse
@@ -182,9 +182,6 @@ Certain features are **disabled** for arbitrary renderables other than strings,
 * Styling with the `"argparse.text"` style defined in `RichHelpFormatter.styles`
 * Replacement of `%(prog)s` with the program name
 
-Arbitrary renderables are displayed "as is" except for long runs of empty lines that get truncated
-to two empty lines following the behavior of argparse.
-
 ## Working with subparsers
 
 Subparsers do not inherit the formatter class from the parent parser by default. You have to pass
@@ -231,11 +228,10 @@ COLUMNS=120 python my_cli.py --generate-help-preview  # force the width of the o
 
 ## Working with third party formatters
 
-*rich-argparse* can be used with other formatters that **do not rely on the private internals**
-of `argparse.HelpFormatter`. A popular example is [django](https://pypi.org/project/django) that
-defines a custom help formatter that is used with its built in commands as well as with extension
-libraries and user defined commands. To use *rich-argparse* in your django project, change your
-`manage.py` file as follows:
+*rich-argparse* can be used with other custom formatters through multiple inheritance. For example,
+[django](https://pypi.org/project/django) defines a custom help formatter for its built in commands
+as well as extension libraries and user defined commands. To use *rich-argparse* in your django
+project, change your `manage.py` file as follows:
 
 ```diff
 diff --git a/my_project/manage.py b/my_project/manage.py
@@ -283,8 +279,7 @@ index 7fb6855..5e5d48a 100755
      main()
 ```
 
-Now try out some command like `python manage.py runserver --help` and notice how the special
-ordering of the arguments applied by django is respected by the new help formatter.
+Now the output of all `python manage.py <COMMAND> --help` will be colored.
 
 ## Optparse support
 
@@ -301,7 +296,7 @@ parser = optparse.OptionParser(formatter=IndentedRichHelpFormatter())
 ...
 ```
 
-You can also generated a more helpful usage message by passing `usage=GENERATE_USAGE` to the
+You can also generate a more helpful usage message by passing `usage=GENERATE_USAGE` to the
 parser. This is similar to the default behavior of `argparse`.
 
 ```python
@@ -322,12 +317,10 @@ Syntax highlighting works the same as with `argparse`.
 
 Colors in the `usage` are only supported when using `GENERATE_USAGE`.
 
-Customizing the group name format is not supported. optparse uses Title Case format by default.
-
 ## Legacy Windows support
 
-If your application still runs on legacy Windows versions (older than Windows 10), you'll need to
-enable ANSI escape sequences by calling `colorama.init()` otherwise colors will be disabled:
+When used on legacy Windows versions like *Windows 7*, colors are disabled unless
+[colorama](https://pypi.org/project/colorama/) is used:
 
 ```python
 import argparse
@@ -338,4 +331,3 @@ colorama.init()
 parser = argparse.ArgumentParser(..., formatter_class=RichHelpFormatter)
 ...
 ```
-This is **not** required on Windows 10 and newer or on other operating systems.