Use content manager to run scripts and user styles

[chorizo.git] / man / chorizo-usage.1.scd

diff --git a/man/chorizo-usage.1.scd b/man/chorizo-usage.1.scd
index 1f7362952afcdfe1d26f8bd6c685c82eb9ca86b9..c21ae1daebe5c0b813de69ac44ee7e7ae74cd83f 100644 (file)
--- a/man/chorizo-usage.1.scd
+++ b/man/chorizo-usage.1.scd
@@ -20,9 +20,9 @@ resume downloads. If a file already exists, it won't be touched. Instead, the
 new file name will have a suffix such as *.1*, *.2*, *.3*, and so on.
 
 # USER-SUPPLIED JAVASCRIPT FILES
-After a page has been successfully loaded, the directory
-_~/.local/share/chorizo/user-scripts_ will be scanned and each file in it ending
-with *.js* will be run as a JavaScript file in the context of said page.
+When a page is being loaded, the directory _~/.local/share/chorizo/user-scripts_
+will be scanned and each file in it ending with *.js* will be run as a
+JavaScript file in the context of said page.
 
 *chorizo* comes with the following scripts:
 
@@ -40,6 +40,11 @@ with *.js* will be run as a JavaScript file in the context of said page.
 Those bundled scripts are automatically installed on *make install*. To use
 them, though, make sure to link them to the directory mentioned above.
 
+# USER-SUPPLIED CSS FILES
+User supplied CSS files will be scanned for from
+_~/.local/share/chorizo/user-styles_, and be applied every time a page
+loads. The rules in these files override any rules provided by the website.
+
 # WEB EXTENSIONS
 On startup, WebKit checks _~/.local/share/chorizo/web_extensions_ for any *.so*
 files. See