[elpa] externals/cape ad13cc9e3a: README: Generate better info output

[ELPA Syncer]

branch: externals/cape
commit ad13cc9e3a505fc3fa56ac559d15e3eca7bcc731
Author: Daniel Mendler <mail@daniel-mendler.de>
Commit: Daniel Mendler <mail@daniel-mendler.de>

    README: Generate better info output
---
 README.org | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/README.org b/README.org
index 61515c7bc9..ca6dbfd6af 100644
--- a/README.org
+++ b/README.org
@@ -12,13 +12,10 @@
 #+html: <a href="https://melpa.org/#/cape";><img alt="MELPA" 
src="https://melpa.org/packages/cape-badge.svg"/></a>
 #+html: <a href="https://stable.melpa.org/#/cape";><img alt="MELPA Stable" 
src="https://stable.melpa.org/packages/cape-badge.svg"/></a>
 
-* Introduction
-
-Cape provides a bunch of Completion At Point Extensions which can be used in
-combination with my [[https://github.com/minad/corfu][Corfu]] completion UI or 
the default completion UI. The
-completion backends used by ~completion-at-point~ are so called
-~completion-at-point-functions~ (Capfs). In principle, the Capfs provided by 
Cape
-can also be used by [[https://github.com/company-mode/company-mode][Company]].
+Cape provides Completion At Point Extensions which can be used in combination
+with the [[https://github.com/minad/corfu][Corfu]] completion UI or the 
default completion UI. The completion
+backends used by ~completion-at-point~ are so called 
~completion-at-point-functions~
+(Capfs). In principle, the Capfs provided by Cape can also be used by 
[[https://github.com/company-mode/company-mode][Company]].
 
 #+html: <img src="https://github.com/minad/cape/blob/logo/cape.png?raw=true"; 
align="right" width="30%">
 
@@ -36,6 +33,8 @@ backends into Capfs and merge multiple Capfs into a 
Super-Capf! These
 transformers allow you to still take advantage of Company backends even if you
 are not using Company as frontend.
 
+#+toc: headlines 8
+
 * Available Capfs
 
 + ~cape-dabbrev~: Complete word from current buffers