remove non ascii whitespaces

technology/applications/web/Gitea.md

@@ -151,9 +151,9 @@ curl --user your_username:your_token_or_password -X DELETE \     https://gitea.e
 ```
 
 ## Profile READMEs
-To display a [Markdown](../../files/Markdown.md) file in your Gitea profile page, simply create a repository named `.profile` and add a new file called `README.md`. Gitea will automatically display the contents of the file on your profile, above your repositories.
+To display a [Markdown](../../files/Markdown.md) file in your Gitea profile page, simply create a repository named `.profile` and add a new file called `README.md`. Gitea will automatically display the contents of the file on your profile, above your repositories.
 
-Making the `.profile` repository private will hide the Profile README.
+Making the `.profile` repository private will hide the Profile README.
 
 ## Docker Compose
 ```yaml

technology/applications/web/Home Assistant.md

@@ -10,9 +10,9 @@ Home Assistant is a local smart home hub platform supportig many [integrations](
 ![Screenshot][Screenshot]
 
 ## Configuration
-While you can configure most of Home Assistant directly from the user interface, some parts need you to edit `configuration.yaml`.
+While you can configure most of Home Assistant directly from the user interface, some parts need you to edit `configuration.yaml`.
 
-To improve readability, you can source out certain domains from your main configuration file with the `!include`-syntax.
+To improve readability, you can source out certain domains from your main configuration file with the `!include`-syntax.
 ```yaml
 light: !include lights.yaml
 ```

technology/applications/web/Uptime Kuma.md

@@ -9,7 +9,7 @@ Uptime Kuma is an easy-to-use self-hosted monitoring tool.
 ## Features
 - Monitoring uptime for [HTTP](../../internet/HTTP.md)(s) / [TCP](../../internet/TCP.md) / [HTTP](../../internet/HTTP.md)(s) Keyword / [HTTP](../../internet/HTTP.md)(s) [Json](../../files/JSON.md) Query / Ping / [DNS](../../internet/DNS.md) Record / Push / Steam Game Server / [Docker](../../tools/Docker.md) Containers
 - Fancy, Reactive, Fast UI/UX
-- Notifications via Telegram, [Discord](../communication/Discord.md), Gotify, Slack, Pushover, [Email](../../internet/eMail.md) ([SMTP](../../internet/SMTP.md)), and 90+ notification services
+- Notifications via Telegram, [Discord](../communication/Discord.md), Gotify, Slack, Pushover, [Email](../../internet/eMail.md) ([SMTP](../../internet/SMTP.md)), and 90+ notification services
 - 20-second intervals
 - Multiple status pages
 - Map status pages to specific domains

technology/applications/web/dufs.md

@@ -46,30 +46,30 @@ Usage: `dufs [OPTIONS] [serve-path]`
 | `--tls-key <path>`      | Path to the SSL/TLS certificate's private key                                                       |
 
 ### Access Control
-Dufs supports account based access control. You can control who can do what on which path with `--auth`/`-a`.
+Dufs supports account based access control. You can control who can do what on which path with `--auth`/`-a`.
 ```
 dufs -a user:pass@/path1:rw,/path2 -a user2:pass2@/path3 -a @/path4
 ```
 
-1. Use `@` to separate the account and paths. No account means anonymous user.
-2. Use `:` to separate the username and password of the account.
-3. Use `,` to separate paths.
-4. Use `:rw` suffix to indicate that the account has read-write permission on the path.
+1. Use `@` to separate the account and paths. No account means anonymous user.
+2. Use `:` to separate the username and password of the account.
+3. Use `,` to separate paths.
+4. Use `:rw` suffix to indicate that the account has read-write permission on the path.
 
 Examples:
-- `-a admin:amdin@/:rw`: `admin` has complete permissions for all paths.
-- `-a guest:guest@/`: `guest` has read-only permissions for all paths.
-- `-a user:pass@/dir1:rw,/dir2`: `user` has complete permissions for `/dir1/*`, has read-only permissions for `/dir2/`.
+- `-a admin:amdin@/:rw`: `admin` has complete permissions for all paths.
+- `-a guest:guest@/`: `guest` has read-only permissions for all paths.
+- `-a user:pass@/dir1:rw,/dir2`: `user` has complete permissions for `/dir1/*`, has read-only permissions for `/dir2/`.
 - `-a @/`: All paths is publicly accessible, everyone can view/download it.
 
 ### Hide Paths
-Dufs supports hiding paths from directory listings via option `--hidden <glob>,...`.
+Dufs supports hiding paths from directory listings via option `--hidden <glob>,...`.
 
 ```
 dufs --hidden .git,.DS_Store,tmp
 ```
 
-> The glob used in --hidden only matches file and directory names, not paths. So `--hidden dir1/file` is invalid.
+> The glob used in --hidden only matches file and directory names, not paths. So `--hidden dir1/file` is invalid.
 
 ```shell
 dufs --hidden '.*'                          # hidden dotfiles
@@ -79,7 +79,7 @@ dufs --hidden '*.log' --hidden '*.lock'
 ```
 
 ### Log Format
-Dufs supports customize [http](../../internet/HTTP.md) log format with option `--log-format`.
+Dufs supports customize [http](../../internet/HTTP.md) log format with option `--log-format`.
 
 The log format can use following variables.
 
@@ -91,13 +91,13 @@ The log format can use following variables.
 | `$status`      | response status                                                               | 
 | `$http_`       | arbitrary request header field. examples: `$http_user_agent`, `$http_referer` |
 
-The default log format is `'$remote_addr "$request" $status'`.
+The default log format is `'$remote_addr "$request" $status'`.
 ```
 2022-08-06T06:59:31+08:00 INFO - 127.0.0.1 "GET /" 200
 ```
 
 ### Environment variables
-All options can be set using [environment variables](../../linux/Environment%20Variables.md) prefixed with `DUFS_`.
+All options can be set using [environment variables](../../linux/Environment%20Variables.md) prefixed with `DUFS_`.
 
 | Option                  | Environment Variable         |
 | ----------------------- | ---------------------------- |
@@ -124,7 +124,7 @@ All options can be set using [environment variables](../../linux/Environment%20V
 | `--tls-key <path>`      | DUFS_TLS_KEY=key.pem         |
 
 ### Configuration File
-You can specify and use the configuration file by selecting the option `--config <path-to-config.yaml>`.
+You can specify and use the configuration file by selecting the option `--config <path-to-config.yaml>`.
 
 The following are the configuration items:
 ```yaml