Move unrelated files out of .config

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

diff --git a/man/lariza-usage.1.scd b/man/lariza-usage.1.scd
index cadf89d2813a5cde517295fbb44d0430cfde37c5..38c03343f897e1e558f490796dcb0ffe467b0727 100644 (file)
--- a/man/lariza-usage.1.scd
+++ b/man/lariza-usage.1.scd
@@ -21,8 +21,8 @@ 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
-_~/.config/lariza/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.
+_~/.local/share/lariza/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.
 
 *lariza* comes with the following scripts:
 
@@ -41,7 +41,7 @@ Those bundled scripts are automatically installed on *make install*. To use
 them, though, make sure to link them to the directory mentioned above.
 
 # WEB EXTENSIONS
-On startup, WebKit checks _~/.config/lariza/web_extensions_ for any *.so*
+On startup, WebKit checks _~/.local/share/lariza/web_extensions_ for any *.so*
 files. See
 <http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/>
 this blog post for further information on these extensions.
@@ -66,8 +66,8 @@ trust additional certificates, such as self-signed certificates, the first thing
 you should do is try to add the appropriate CAs to your system-wide store.
 
 If you wish to add simple exceptions, you can grab the certificate and store it
-in the directory _~/.config/lariza/certs_. The filename must be equal to the
-hostname:
+in the directory _~/.local/share/lariza/certs_. The filename must be equal to
+the hostname:
 
        $ echo | openssl s_client -connect foo.de:443 | openssl x509 >foo.de