chore: a large number of typo corrections in markdown files

doc/book/connect/_index.md

@@ -23,7 +23,7 @@ To configure S3-compatible software to interact with Garage,
 you will need the following parameters:
 
 - An **API endpoint**: this corresponds to the HTTP or HTTPS address
-  used to contact the Garage server. When runing Garage locally this will usually
+  used to contact the Garage server. When running Garage locally this will usually
   be `http://127.0.0.1:3900`. In a real-world setting, you would usually have a reverse-proxy
   that adds TLS support and makes your Garage server available under a public hostname
   such as `https://garage.example.com`.

doc/book/connect/apps/index.md

@@ -54,7 +54,7 @@ garage bucket allow nextcloud --read --write --key nextcloud-key
 
 Now edit your Nextcloud configuration file to enable object storage.
 On my installation, the config. file is located at the following path: `/var/www/nextcloud/config/config.php`.  
-We will add a new root key to the `$CONFIG` dictionnary named `objectstore`:
+We will add a new root key to the `$CONFIG` dictionary named `objectstore`:
 
 ```php
 <?php
@@ -413,7 +413,7 @@ mc mirror --newer-than "3h" ./public/system/ garage/mastodon-data
 
 ## Matrix
 
-Matrix is a chat communication protocol. Its main stable server implementation, [Synapse](https://matrix-org.github.io/synapse/latest/), provides a module to store media on a S3 backend. Additionally, a server independent media store supporting S3 has been developped by the community, it has been made possible thanks to how the matrix API has been designed and will work with implementations like Conduit, Dendrite, etc.
+Matrix is a chat communication protocol. Its main stable server implementation, [Synapse](https://matrix-org.github.io/synapse/latest/), provides a module to store media on a S3 backend. Additionally, a server independent media store supporting S3 has been developed by the community, it has been made possible thanks to how the matrix API has been designed and will work with implementations like Conduit, Dendrite, etc.
 
 ### synapse-s3-storage-provider (synapse only)
 
@@ -450,7 +450,7 @@ media_storage_providers:
 
 Note that uploaded media will also be stored locally and this behavior can not be deactivated, it is even required for
 some operations like resizing images.
-In fact, your local filesysem is considered as a cache but without any automated way to garbage collect it.
+In fact, your local filesystem is considered as a cache but without any automated way to garbage collect it.
 
 We can build our garbage collector with `s3_media_upload`, a tool provided with the module.
 If you installed the module with the command provided before, you should be able to bring it in your path:
@@ -646,7 +646,7 @@ s3:
     b2-eu-cen: # Don't change this key, it is hardcoded
         key: <keyID> 
         secret: <keySecret>
-        endpoint: garage:3900 # publically accessible endpoint of your garage instance
+        endpoint: garage:3900 # publicly accessible endpoint of your garage instance
         region: garage
         bucket: <yourbucketName>
         use_path_style: true
@@ -730,7 +730,7 @@ Pleroma have an internal migration tool that can encounter some fatal error
 
 So, use [your best tool](https://garagehq.deuxfleurs.fr/documentation/connect/cli/) to sync `/var/lib/pleroma/uploads/` in your S3.
 
-Then, to avoid some non existant problem (just in case of), run this command
+Then, to avoid some non existent problem (just in case of), run this command
 
 ```bash
 while true

doc/book/connect/cli.md

@@ -41,7 +41,7 @@ Some commands:
 # list buckets
 mc ls garage/
 
-# list objets in a bucket
+# list objects in a bucket
 mc ls garage/my_files
 
 # copy from your filesystem to garage
@@ -218,7 +218,7 @@ Within Cyberduck, a
 available within the `Preferences -> Profiles` section. This can enabled and
 then connections to Garage may be configured.
 
-### Instuctions for the CLI
+### Instructions for the CLI
 
 To configure duck (Cyberduck's CLI tool), start by creating its folder hierarchy:
 

doc/book/connect/repositories.md

@@ -201,11 +201,9 @@ on the binary cache, the client will download the result from the cache instead
 
 ### Channels
 
-Channels additionnaly serve Nix definitions, ie. a `.nix` file referencing
+Channels additionally serve Nix definitions, ie. a `.nix` file referencing
 all the derivations you want to serve.
 
 ## Gitlab
 
 *External link:* [Gitlab Documentation > Object storage](https://docs.gitlab.com/ee/administration/object_storage.html)
-
-