Remove some more horrifying hyphens.

supahgreg · supahgreg · commit 9dd68ec43937 · 2025-11-10T02:42:21.000Z
diff --git a/docs/API-Reference.md b/docs/API-Reference.md
@@ -127,11 +127,11 @@ password parameters.
 
 - On version:1.6.0 and above login also returns current API level as an
   <code>api\_level</code> integer, you can use that instead of calling `getApiLevel` after login.
-- Since API 17, also returns configuration object (see `getConfig`-below).
+- Since API 17, also returns configuration object (see [`getConfig`](#getconfig) below).
 
 ### logout
 
-Closes your login session. Returns either status message <code>{"status":"OK"}</code> or an error (e.g.-<code>{"error":"NOT_LOGGED_IN"}</code>)
+Closes your login session. Returns either status message <code>{"status":"OK"}</code> or an error (e.g. <code>{"error":"NOT_LOGGED_IN"}</code>)
 
 ### isLoggedIn
 
@@ -172,7 +172,7 @@ instead.
 Special category IDs are as follows:
 
 * 0 Uncategorized
-* -1 Special (e.g. Starred, Published, Archived,-etc.)
+* -1 Special (e.g. Starred, Published, Archived, etc.)
 * -2 Labels
 
 Added in version:1.5.0:
@@ -215,7 +215,7 @@ Parameters:
 - ``is_cat`` (bool) - requested `feed_id` is a category
 - ``show_excerpt`` (bool) - include article excerpt in the output
 - ``show_content`` (bool) - include full article text in the output
-- ``view_mode`` (string = all\_articles, unread, adaptive,-marked,
+- ``view_mode`` (string = all\_articles, unread, adaptive, marked,
     updated)
 - ``include_attachments`` (bool) - include article attachments (e.g.
     enclosures) **requires version:1.5.3**
@@ -233,7 +233,7 @@ Parameters:
     elements **<span class="10 api"></span>** (default: false)
 - ``include_header`` (bool) - adds status information when returning
     headlines, instead of array(articles) return value changes to
-    array(header,-array(articles)) (api 12)
+    array(header, array(articles)) (api 12)
 
 Limit:
 
@@ -411,7 +411,7 @@ Parameters:
 Note: Up until version:1.15 setArticleLabel() clears the label cache for
 the specified articles. Make sure to regenerate it (e.g. by calling API
 method getLabels() for the respecting articles) when you&rsquo;re using
-methods which don&rsquo;t do that by themselves (e.g.-getHeadlines())
+methods which don&rsquo;t do that by themselves (e.g. getHeadlines())
 otherwise getHeadlines() will not return labels for modified articles.
 
 ### shareToPublished (since API level 4 --version:1.6.0)
@@ -433,7 +433,7 @@ subscribe\_to\_feed() in functions.php for details.
 Parameters:
 
 * ``feed_url`` - Feed URL (string)
-* ``category_id`` - Category id to place feed into (defaults to 0,-Uncategorized) (int)
+* ``category_id`` - Category id to place feed into (defaults to 0, Uncategorized) (int)
 * ``login``, ``password`` - Self explanatory (string)
 
 ### unsubscribeFeed (API level 5 --version:1.7.6)
diff --git a/docs/Content-Filters.md b/docs/Content-Filters.md
@@ -37,7 +37,7 @@ final matching.
 all rules match.
 - Regular expressions may be matched against several article fields, such
 as, title, content, author, etc.
-- Do not include delimiters (e.g.-<code>/</code>) when writing regular
+- Do not include delimiters (e.g. <code>/</code>) when writing regular
 expressions.
 
 ### Matching articles and applying actions
diff --git a/docs/FAQ.md b/docs/FAQ.md
@@ -37,9 +37,9 @@ This sets your password back to default (``password``) and disables OTP.
 
 The problem is that if you have `auth_remote` enabled in [PLUGINS](Global-Config) tt-rss tries to automatically log you in as the user specified by the server using HTTP authentication, which may not have administrative privileges.
 
-The easiest way is simply updating database using CLI (`php ./update.php---update-schema`). Docker setup does this on startup.
+The easiest way is simply updating database using CLI (`php ./update.php --update-schema`). Docker setup does this on startup.
 
-Alternatively, you can either temporarily disable `auth_remote` (replace it with-`auth_internal`), temporarily disable HTTP authentication, or give yourself administrative permissions using SQL:
+Alternatively, you can either temporarily disable `auth_remote` (replace it with `auth_internal`), temporarily disable HTTP authentication, or give yourself administrative permissions using SQL:
 
 ```sql
     update ttrss_users set access_level = 10 where login = 'you';
@@ -105,7 +105,7 @@ Related question:
 
 Because the articles are still in the feed XML and get pulled in (again) on next feed update.
 
-See-also: [Archived Feed](Archived-Feed.md)
+See also: [Archived Feed](Archived-Feed.md)
 
 ### I have used update daemon before, but switched away from it. However, the UI keeps nagging me about the daemon not running or not updating feeds or whatever
 
diff --git a/docs/Generated-Feeds.md b/docs/Generated-Feeds.md
@@ -5,7 +5,7 @@ parent: Features
 ---
 
 You can generate a feed (in Atom or JSON format) for almost anything displayed
-in headlines buffer (e.g. actual feeds, Labels, Categories,-etc.) by clicking
+in headlines buffer (e.g. actual feeds, Labels, Categories, etc.) by clicking
 this icon:
 
 ![Generated feed icon](../images/gen_feed_icon.png)
@@ -58,7 +58,7 @@ Feed ID values less than `-10` are considered Labels.
 ### Special category IDs (is\_cat=1)
 
 - ``0`` - Uncategorized
-- ``-1`` - Special category (includes Starred, Published,-etc.)
+- ``-1`` - Special category (includes Starred, Published, etc.)
 - ``-2`` - Labels category (includes your labels)
 
 ### View mode values
@@ -78,9 +78,9 @@ specifier because unread articles are never part of the feed).
 
 ### Order values
 
-- ``default`` - depends on the feed: either import batch date or (for published and starred-feeds) ``last_published`` and ``last_marked``
+- ``default`` - depends on the feed: either import batch date or (for published and starred feeds) ``last_published`` and ``last_marked``
 - ``title`` - sort by title
 - ``date_reverse`` - reverse sort by batch date
 - ``feed_dates`` - sort by feed-provided article dates
 
-See-also: [Publish Articles](Publish-Articles.md)
+See also: [Publish Articles](Publish-Articles.md)
diff --git a/docs/Global-Config.md b/docs/Global-Config.md
@@ -32,7 +32,7 @@ putenv('TTRSS_SESSION_COOKIE_LIFETIME='.(86400*30));
 Legacy plugin-required constants also go to `config.php`, using `define()`:
 
 ```js
-define('LEGACY_CONSTANT',-'value');
+define('LEGACY_CONSTANT', 'value');
 ```
 
 To set computed values via `putenv()` you have to get them evaluated by PHP, this would work:
diff --git a/docs/Installation-Guide.md b/docs/Installation-Guide.md
@@ -16,9 +16,9 @@ nav_order: 2
 
 The main (and recommended) way to run tt-rss is under Docker.
 
-Docker images for <https://github.com/tt-rss/tt-rss> are being built (for `linux/amd64` and-`linux/arm64`) and published
+Docker images for <https://github.com/tt-rss/tt-rss> are being built (for `linux/amd64` and `linux/arm64`) and published
 ([via GitHub-Actions](https://github.com/tt-rss/tt-rss/actions/workflows/publish.yml)) to:
-* Docker Hub (as-[supahgreg/tt-rss](https://hub.docker.com/r/supahgreg/tt-rss/) and [supahgreg/tt-rss-web-nginx](https://hub.docker.com/r/supahgreg/tt-rss-web-nginx/)).
+* Docker Hub (as [supahgreg/tt-rss](https://hub.docker.com/r/supahgreg/tt-rss/) and [supahgreg/tt-rss-web-nginx](https://hub.docker.com/r/supahgreg/tt-rss-web-nginx/)).
 * GitHub Container Registry (as-[ghcr.io/tt-rss/tt-rss](https://github.com/orgs/tt-rss/packages/container/package/tt-rss)
   and [ghcr.io/tt-rss/tt-rss-web-nginx](https://github.com/orgs/tt-rss/packages/container/package/tt-rss-web-nginx)).
 
@@ -245,7 +245,7 @@ Don't forget to remove `/tt-rss/` from `TTRSS_SELF_URL_PATH`.
 
 ### How do I apply configuration options?
 
-There are two sets of options you can change through the environment - options specific to tt-rss (those are prefixed with-`TTRSS_`) and options affecting container behavior.
+There are two sets of options you can change through the environment: those specific to tt-rss (those are prefixed with-`TTRSS_`) and those affecting container behavior.
 
 #### Options specific to tt-rss
 
diff --git a/docs/Making-Plugins.md b/docs/Making-Plugins.md
@@ -6,7 +6,7 @@ nav_order: 1
 ---
 
 Plugins may render new preference panes or embed themselves into several
-existing one, store data using simple key -\> value data or directly in
+existing one, store data using simple key/value data or directly in
 the database, modify how articles are rendered, alter feed data, and
 much more.
 
diff --git a/docs/Plugins.md b/docs/Plugins.md
@@ -16,7 +16,7 @@ configuration](Global-Config) directive <code>PLUGINS</code> which is a
 comma-separated list of enabled system plugins, i.e.
 
 ```js
-putenv('TTRSS_PLUGINS=auth_internal,-other_plugin');
+putenv('TTRSS_PLUGINS=auth_internal, other_plugin');
 ```
 
 System plugins are always enabled for all users. If multiple search plugins are loaded, only the first one is used
diff --git a/docs/SSL-Certificate-Authentication.md b/docs/SSL-Certificate-Authentication.md
@@ -17,7 +17,7 @@ You **must** have a working tt-rss installation with SSL. This guide is not inte
 
 If you have no idea how certificates work (i.e. the terms x509 and PKI make no sense to you), stop now.
 
-This guide includes steps for Nginx. Of course other web servers (e.g.-Apache) support client certificates so you're welcome to use them if you prefer, the steps just aren't included here (but might be added at some point).
+This guide includes steps for Nginx. Of course other web servers (e.g. Apache) support client certificates so you're welcome to use them if you prefer, the steps just aren't included here (but might be added at some point).
 
 This guide was written with Debian 9 in mind, other distros will vary.
 
@@ -28,7 +28,7 @@ Client certificates are typically created/issued by a private Certificate Author
 create a root certificate authority and install the **public** certificate for it on
 your web server. You then create certificates for each client, signed by the root
 certificate authority's private key. Each client is issued their certificate and
-private key (often as a single file with a `.p12`-extension).
+private key (often as a single file with a `.p12` extension).
 
 Note:
 
@@ -85,12 +85,12 @@ sudo systemctl restart nginx
 Update the tt-rss config file to add `auth_remote` to the `PLUGINS` constant (near the end of the file):
 
 ```php
-define('PLUGINS', 'auth_internal, auth_remote,-note');
+define('PLUGINS', 'auth_internal, auth_remote, note');
 ```
 
 You might be tempted to remove `auth_internal` but we still need it so don't.
 
-Next, make sure your client certificate (the `.p12`-file) is installed on your
+Next, make sure your client certificate (the `.p12` file) is installed on your
 computer. Different operating systems and browsers do this differently, so you're
 pretty much on your own there. However, if you double-click the .p12 file from the
 desktop, the operating system should offer to install it for you.
diff --git a/docs/Search-Syntax.md b/docs/Search-Syntax.md
@@ -11,7 +11,7 @@ Search query consists of several keywords. Keyword starting with "-" is consider
 * ``@{date}`` - match by date. For example, @yesterday or @2011-11-03. Please note that due to incomplete implementation, special date keywords like yesterday might not match all articles if user timezone is different from tt-rss internal timezone (UTC).
 * ``pub:{true,false}`` - match only published or unpublished articles
 * ``star:{true, false}`` - same, starred articles
-* ``unread:{true, false}`` - self explanatory (requires trunk as of-05.03.2015)
+* ``unread:{true, false}`` - self explanatory (requires trunk as of 05.03.2015)
 * ``note:{true, false, sometext}`` - same, for articles having an attached note or matching the specified text
 * ``label:Somelabel`` - articles that belong to a specified label
 * ``tag:mytag`` - articles which have specified tag
@@ -21,4 +21,4 @@ When searching by keyword with spaces, use quotes like this: `"title:string with
 
 If no special keywords are specified, search is done using PostgreSQL [Full Text Search](https://www.postgresql.org/docs/current/textsearch-intro.html) engine.
 
-Pointless as it may be, you can combine negative prefix with the special keywords: -star:true would essentially mean star:false.
+Pointless as it may be, you can combine negative prefix with the special keywords: `-star:true` would essentially mean `star:false`.
diff --git a/docs/Securing-Cache-Directories.md b/docs/Securing-Cache-Directories.md
@@ -28,7 +28,7 @@ location = /tt-rss/config.php {
 
 Note: official docker setup has this out of the box.
 
-## Using apache (2.4-syntax)
+## Using apache (2.4 syntax)
 
 ```apache
 <Directory /var/www/html/tt-rss/cache>
