X-Git-Url: https://git.madduck.net/etc/vim.git/blobdiff_plain/f1f12284e0e9424890b2616b198e69ed7e147116..07b1b2f3dd0e4f13dd5df96eb9188f3d02f5726e:/README.md?ds=sidebyside

diff --git a/README.md b/README.md
index f3a9bb8..5b5903b 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@ possible.
 
 ---
 
-*Contents:* **[Installation and Usage](#installation-and-usage)** |
+*Contents:* **[Installation and usage](#installation-and-usage)** |
 **[The *Black* code style](#the-black-code-style)** |
 **[Editor integration](#editor-integration)** |
 **[Version control integration](#version-control-integration)** |
@@ -380,7 +380,7 @@ decision = (maybe.this() and values > 0) or (maybe.that() and values < 0)
 
 Some popular APIs, like ORMs, use call chaining.  This API style is known
 as a [fluent interface](https://en.wikipedia.org/wiki/Fluent_interface).
-*Black* formats those treating dots that follow a call or an indexing
+*Black* formats those by treating dots that follow a call or an indexing
 operation like a very low priority delimiter.  It's easier to show the
 behavior than to explain it.  Look at the example:
 ```py3
@@ -654,7 +654,19 @@ More details can be found in [CONTRIBUTING](CONTRIBUTING.md).
 ### 18.5b1 (unreleased)
 
 * Python grammar pickle caches are stored with the formatting caches, making
-  *Black* work in environments where site-packages is not user-writable (#192).
+  *Black* work in environments where site-packages is not user-writable (#192)
+
+* fixed invalid code produced when standalone comments were present in a trailer
+  that was omitted from line splitting on a large expression (#237)
+
+* fixed optional parentheses being removed within `# fmt: off` sections (#224)
+
+* fixed invalid code produced when stars in very long imports were incorrectly
+  wrapped in optional parentheses (#234)
+
+* fixed unstable formatting when inline comments were moved around in
+  a trailer that was omitted from line splitting on a large expression
+  (#238) 
 
 ### 18.5b0