fixup! news: 0.5.1

Author: justinmk

_posts/2021-09-26-newsletter.md

@@ -6,7 +6,8 @@ permalink: /news/2021/09
 ---
 
 > The Citadel stripped me of it. They found some of my... experiments... too bold.
-—Qyburn
+>
+> —Qyburn
 
 Nvim 0.5.1 has been released, it includes many fixes and some breaking changes:
 
@@ -72,14 +73,26 @@ Your feedback helps us.  We considered removing the 'backspace' option and decid
 
 ## Engineering
 
-`vim.mpack` now exposes a Lua-first messagepack encoder/decoder without marshalling through Vimscript. This also sets the stage for eliminating a dependency on libmsgpack in favor of libmpack.
+`vim.mpack` now exposes a Lua-first messagepack encoder/decoder without
+marshalling through Vimscript. This also sets the stage for eliminating
+a dependency on libmsgpack in favor of libmpack.
 
-`vim.json` exposes a Lua-first JSON encoder/decoder without marshalling through Vimscript. This performance gain is helpful in the LSP client, where JSON de/serialization dominates the cost of many client activities.
+`vim.json` exposes a Lua-first JSON encoder/decoder without marshalling through
+Vimscript. This performance gain is helpful in the LSP client, where JSON
+de/serialization dominates the cost of many client activities.
 
-Nvim core team has fully migrated to GitHub Actions for CI, and we are leaning heavily on this to automate even more of our workflow.
+Nvim core team has fully migrated to GitHub Actions for CI, and we are leaning
+heavily on this to automate even more of our workflow.
 
-Nvim C source code is now fully reformatted to match our [style guide](https://neovim.io/doc/user/dev_style.html#dev-style), so that our development workflow favors auto-formatting instead of tedious human-driven compliance with the style guide.  This is especially important for reducing friction of merging patches from upstream Vim.
+Nvim C source code is now fully reformatted to match our [style
+guide](https://neovim.io/doc/user/dev_style.html#dev-style), so that our
+development workflow favors auto-formatting instead of tedious human-driven
+compliance with the style guide.  This is especially important for reducing
+friction of merging patches from upstream Vim.
 
+Upstream improvements in libuv and Windows 10 allow us to eliminate our [libuv
+fork](https://github.com/neovim/libuv).  Note that going forward we consider
+**Windows 8 or older is unsupported,** particularly for TUI/TTY bug reports.
 
 ### Vim patches