[elpa] externals/cape a35d699196: README: Be more explicit about cape-super-capf (See #69)

[ELPA Syncer]

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

    README: Be more explicit about cape-super-capf (See #69)
---
 README.org | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/README.org b/README.org
index aa853aa480..881c5c2c17 100644
--- a/README.org
+++ b/README.org
@@ -169,9 +169,8 @@ then be used as a Capf via ~cape-company-to-capf~.
 
 /Throw multiple Capfs under the Cape and get a Super-Capf!/
 
-Cape supports merging multiple Capfs using the function ~cape-super-capf~. This
-feature is experimental and should only be used in special scenarios.
-*Don't use cape-super-capf if you are not 100% sure that you need it!*
+Cape supports merging multiple Capfs using the function ~cape-super-capf~.
+*This feature is EXPERIMENTAL and should only be used in special scenarios. 
Don't use cape-super-capf if you are not 100% sure that you need it! If you 
decide to use the function, you are on UNSUPPORTED TERRITORY.*
 
 Note that ~cape-super-capf~ is not needed if you want to use multiple Capfs 
which
 are tried one by one, e.g., it is perfectly possible to use ~cape-file~ 
together