fix(docs): typos

Apply patch from https://github.com/go-vikunja/vikunja/issues/263

docs/content/doc/setup/config.md

@@ -348,6 +348,7 @@ Environment path: `VIKUNJA_SERVICE_CUSTOMLOGOURL`
 
 ### enablepublicteams
 
+Enables the public team feature. If enabled, it is possible to configure teams to be public, which makes them
 discoverable when sharing a project, therefore not only showing teams the user is member of.
 
 Default: `false`
@@ -779,7 +780,7 @@ Environment path: `VIKUNJA_MAILER_PASSWORD`
 
 ### skiptlsverify
 
-Wether to skip verification of the tls certificate on the server
+Whether to skip verification of the tls certificate on the server
 
 Default: `false`
 
@@ -1222,7 +1223,7 @@ OpenID configuration will allow users to authenticate through a third-party Open
 The provider needs to support the `openid`, `profile` and `email` scopes.<br/>
 **Note:** Some openid providers (like Gitlab) only make the email of the user available through OpenID if they have set it to be publicly visible.
 If the email is not public in those cases, authenticating will fail.
-**Note 2:** The frontend expects the third party to rediect the user <frontend-url>/auth/openid/<auth key> after authentication. Please make sure to configure the redirect url in your third party auth service accordingly if you're using the default vikunja frontend.
++**Note 2:** The frontend expects the third party to redirect the user <frontend-url>/auth/openid/<auth key> after authentication. Please make sure to configure the redirect url in your third party auth service accordingly if you're using the default vikunja frontend.    
 The frontend will automatically provide the API with the redirect url, composed from the current url where it's hosted.
 If you want to use the desktop client with OpenID, make sure to allow redirects to `127.0.0.1`.
 Take a look at the [default config file](https://kolaente.dev/vikunja/vikunja/src/branch/main/config.yml.sample) for more information about how to configure openid authentication.
@@ -1421,15 +1422,15 @@ Full path: `webhooks.enabled`
 Environment path: `VIKUNJA_WEBHOOKS_ENABLED`
 
 
-### timoutseconds
+### timeoutseconds
 
-The timout in seconds until a webhook request fails when no response has been received.
+The timeout in seconds until a webhook request fails when no response has been received.
 
 Default: `30`
 
-Full path: `webhooks.timoutseconds`
+Full path: `webhooks.timeoutseconds`
 
-Environment path: `VIKUNJA_WEBHOOKS_TIMOUTSECONDS`
+Environment path: `VIKUNJA_WEBHOOKS_TIMEOUTSECONDS`
 
 
 ### proxyurl

docs/content/doc/setup/full-docker-example.md

@@ -40,7 +40,7 @@ chown 1000 $PWD/files
 
 You'll need to do this before running any of the examples on this page.
 
-Vikunja will not try to aquire ownership of the files folder, as that would mean it had to run as root.
+Vikunja will not try to acquire ownership of the files folder, as that would mean it had to run as root.
 
 ## PostgreSQL
 
@@ -312,7 +312,7 @@ To do that, you can
 
 * Either activate SSH and paste the adapted compose file in a terminal (using Putty or similar)
 * Without activating SSH as a "custom script" (go to Control Panel / Task Scheduler / Create / Scheduled Task / User-defined script)
-* Without activating SSH, by using Portainer (you have to install first, check out [this tutorial](https://www.portainer.io/blog/how-to-install-portainer-on-a-synology-nas) for exmple):
+* Without activating SSH, by using Portainer (you have to install first, check out [this tutorial](https://www.portainer.io/blog/how-to-install-portainer-on-a-synology-nas) for example):
   1. Go to **Dashboard / Stacks** click the button **"Add Stack"**
   2. Give it the name Vikunja and paste the adapted docker compose file
   3. Deploy the Stack with the "Deploy Stack" button:

docs/content/doc/setup/install.md

@@ -37,7 +37,7 @@ This document provides an overview and instructions for the different methods:
 * [FreeBSD](#freebsd--freenas)
 * [Kubernetes]({{< ref "k8s.md" >}})
 
-And after you installed Vikunja, you may want to check out these other ressources:
+And after you installed Vikunja, you may want to check out these other resources:
 
 * [Configuration]({{< ref "config.md">}})
 * [UTF-8 Settings]({{< ref "utf-8.md">}})
@@ -229,7 +229,7 @@ git clone https://code.vikunja.io/vikunja
 cd vikunja
 ```
 
-**Note:** Ceck out the version you want to build with `git checkout VERSION` - replace `VERSION` with the version want to use.
+**Note:** Check out the version you want to build with `git checkout VERSION` - replace `VERSION` with the version want to use.
 If you don't do this, you'll build the [latest unstable build]({{< ref "versions.md">}}), which might contain bugs.
 
 ### Compile binaries

docs/content/doc/setup/openid.md

@@ -17,7 +17,7 @@ Vikunja allows for authentication with an external identity source such as Authe
 
 ## OpenID Connect Overview
 
-OpenID Connect is a standardized identity layer built on top of the more generic OAuth 2.0 specification, simplying interaction between the involved parties significantly.
+OpenID Connect is a standardized identity layer built on top of the more generic OAuth 2.0 specification, simplifying interaction between the involved parties significantly.
 While the [OpenID specification](https://openid.net/specs/openid-connect-core-1_0.html#Overview) is worth a read, we summarize the most important basics here.
 
 The involved parties are:

docs/content/doc/setup/subdirectory.md

@@ -17,7 +17,7 @@ However, you can still run it in a subdirectory but need to build the frontend y
 First, make sure you're able to build the frontend from source.
 Check [the guide about building from source]({{< ref "build-from-source.md">}}#frontend) about that.
 
-### Dynamicly set with build command
+### Dynamically set with build command
 
 Run the build with the `VIKUNJA_FRONTEND_BASE` variable specified.