Merge branch 'main' of github.com:hedyhli/outline.nvim

doc/outline.txt

@@ -452,7 +452,7 @@ requirements) 1. Norg (requires `norg` parser for treesitter)
 
 External providers: - Asciidoc
 <https://github.com/msr1k/outline-asciidoc-provider.nvim> (no external
-requirements) - treesitter
+requirements) - Treesitter
 <https://github.com/epheien/outline-treesitter-provider.nvim> (require
 treesitter) - ctags <https://github.com/epheien/outline-ctags-provider.nvim>
 (require universal-ctags)
@@ -1111,15 +1111,10 @@ RELATED PLUGINS                                      *outline-related-plugins*
     a few example use-cases where you may want to use Aerial, and others
     Outline.nvim.
     Aerial does a great job at supercharging vim’s built-in outline (`gO`). It
-    supports treesitter and manpages which Outline.nvim does not provide
-    |outline-by-default|. (Note that Aerial also supports Norg through treesitter
-    like Outline.nvim, but as of writing it does not support JSX like Outline.nvim
-    does.)
-    - If you wish to prioritize treesitter as the provider ("backend" in Aerial’s
-        terms) for your symbols, you should use Aerial. This lets you have symbols
-        for languages that you might not want to set up an LSP for, which is quite
-        useful. Treesitter support is a planned feature in Outline.nvim but might
-        not arrive very soon.
+    supports treesitter which Outline.nvim does not provide |outline-by-default|,
+    but can be added an external provider. (Note that Aerial also supports Norg
+    through treesitter like Outline.nvim, but as of writing it does not support JSX
+    like Outline.nvim does.)
     - Aerial.nvim supports only Neovim 0.8 and above for the bleeding-edge
         features, as far as I know. You should use Outline.nvim (or the
         alternatives below) if you use Neovim 0.7 and wish to have equal support.