docs - fix typos

docs/README.md

@@ -21,9 +21,9 @@ Neko is also a great tool for **hosting watch parties** and interactive presenta
 
 ## About
 
-This app uses WebRTC to stream a desktop inside of a docker container, original author made this because [rabb.it](https://en.wikipedia.org/wiki/Rabb.it) went under and his internet could not handle streaming and discord kept crashing when his friend attempted to. He just wanted to watch anime with his friends ლ(ಠ益ಠლ) so he started digging throughout the internet and found a few *kinda* clones, but none of them had the virtual browser, then he found [Turtus](https://github.com/Khauri/Turtus) and he was able to figure out the rest.
+This app uses WebRTC to stream a desktop inside a docker container, original author made this because [rabb.it](https://en.wikipedia.org/wiki/Rabb.it) went under, and his internet could not handle streaming and discord kept crashing when his friend attempted to. He just wanted to watch anime with his friends ლ(ಠ益ಠლ) so he started digging throughout the internet and found a few *kinda* clones, but none of them had the virtual browser, then he found [Turtus](https://github.com/Khauri/Turtus), and he was able to figure out the rest.
 
-Then I found [this](https://github.com/nurdism/neko) project and started to dig into it. I really liked the idea of having collaborative browser browsing together with mutliple people, so I created a fork. Initially, I wanted to merge my changes to the upstream repository, but the original author did not have time for this project anymore and it got eventually archived.
+Then I found [this](https://github.com/nurdism/neko) project and started to dig into it. I really liked the idea of having collaborative browser browsing together with multiple people, so I created a fork. Initially, I wanted to merge my changes to the upstream repository, but the original author did not have time for this project anymore, and it got eventually archived.
 
 ### Features
 
@@ -41,4 +41,4 @@ Then I found [this](https://github.com/nurdism/neko) project and started to dig
 
 I like cats 🐱 (`Neko` is the Japanese word for cat), I'm a weeb/nerd.
 
-***But why the cat butt?*** Because cats are *assholes*, but you love them anyways.
+***But why the cat butt?*** Because cats are *assholes*, but you love them anyway.

docs/getting-started/README.md

@@ -48,7 +48,7 @@ All images are also available on [GitHub Container Registry](https://github.com/
 - `ghcr.io/m1k1o/neko/vlc:latest`
 - `ghcr.io/m1k1o/neko/xfce:latest`
 
-For ARM-based images (like Raspberry Pi - with GPU hardware acceleration, Oracle Cloud ARM tier). Currently not all images are available for ARM, because not all applications are available for ARM.
+For ARM-based images (like Raspberry Pi - with GPU hardware acceleration, Oracle Cloud ARM tier). Currently, not all images are available for ARM, because not all applications are available for ARM.
 
 - `ghcr.io/m1k1o/neko/arm-firefox:latest`
 - `ghcr.io/m1k1o/neko/arm-chromium:latest`
@@ -145,7 +145,7 @@ services:
 - For other chromium based browsers, see in `supervisord.conf` folder that is specified in `--user-data-dir`.
 
 #### Allow persistent data in policies
-- From security perespective, browser is set up to forget all cookies and browsing history when its closed.
+- From security perspective, browser is set up to forget all cookies and browsing history when its closed.
 - If you want to enable this, you need to modify following policies:
 ```json
   "DefaultCookiesSetting": 1,

docs/getting-started/configuration.md

@@ -136,7 +136,7 @@ nat1to1: <ip>
   - Enable file transfer feature.
   - e.g. `true`
 #### `NEKO_FILE_TRANSFER_PATH`:
-  - Path where files will be transferred between the host and users. By default this is
+  - Path where files will be transferred between the host and users. By default, this is
   `/home/neko/Downloads`. If the path doesn't exist, it will be created.
   - e.g. `/home/neko/Desktop`
 

docs/getting-started/reverse-proxy.md

@@ -42,9 +42,9 @@ server {
 
 After successfully installing and running neko, you might want to get rid of the port in the url, use DNS instead of IP address and also having SSL.
 This will remove the port from the URL and also enables HTTPS.
-To do this, you have to get running apache server. Now you can go into the `/etc/apache2/sites-available` folder and create new config file for example `neko.conf`
+To do this, you have to get running Apache server. Now you can go into the `/etc/apache2/sites-available` folder and create new config file for example `neko.conf`
-After creating new config file, you can use this example config and paste it in. Some thing might vary on your machine so read through and modify if needed.
+After creating new config file, you can use this example config and paste it in. Some things may vary on your machine so read through and modify if needed.
-Bear in mind that your neko server doesn't have to run on the same computer as apache. They just have to be on the same network and then you replace localhost with correct internal IP.
+Bear in mind that your neko server doesn't have to run on the same computer as Apache. They just have to be on the same network, and then you replace localhost with correct internal IP.
 
 ```xml
 <VirtualHost *:80>

docs/getting-started/troubleshooting.md

@@ -1,6 +1,6 @@
 # Troubleshooting
 
-Neko UI loads but you don't see the screen and it gives you `connection timeout` or `disconnected` error?
+Neko UI loads, but you don't see the screen, and it gives you `connection timeout` or `disconnected` error?
 
 ## Test your client
 
@@ -42,7 +42,7 @@ services:
 
 Ensure, that your ports are reachable through your external IP.
 
-To validate UDP connection the simpliest way, run this on your server:
+To validate UDP connection the simplest way, run this on your server:
 
 ```shell
 nc -ul 52101
@@ -61,7 +61,7 @@ If it does not work for you, then most likely your port forwarding is not workin
 
 ### Check if your external IP was determined correctly
 
-One of the first logs, when the server starts, writes down your external IP that will be sent to your clients to conenct to.
+One of the first logs, when the server starts, writes down your external IP that will be sent to your clients to connect to.
 
 ```shell
 docker-compose logs neko | grep nat_ips
@@ -73,7 +73,7 @@ You should see this:
 11:11AM INF webrtc starting ephemeral_port_range=52000-52100 ice_lite=true ice_servers="[{URLs:[stun:stun.l.google.com:19302] Username: Credential:<nil> CredentialType:password}]" module=webrtc nat_ips=<your-IP>
 ```
 
-If your IP is not correct, you can specify own IP resover using `NEKO_IPFETCH`. It needs to return IP address that will be used.
+If your IP is not correct, you can specify own IP resolver using `NEKO_IPFETCH`. It needs to return IP address that will be used.
 
 ```diff
 version: "3.4"
@@ -119,13 +119,13 @@ If you want to use n.eko only locally, you must put here your local IP address,
 
 ### Neko works externally, but not locally
 
-You are probabbly missing NAT Loopback (NAT Hairpinning) setting on your router.
+You are probably missing NAT Loopback (NAT Hairpinning) setting on your router.
 
 Example for pfsense with truecharts docker container:
 - First, port forward the relevant ports 8080 and 52000-52100/udp for the container.
 - Then turn on `Pure NAT` pfsense (under system > advanced > firewall and nat).
   - Make sure to check the two boxes so it works.
-- Make sure `NEKO_NAT1TO1` is blank and `NEKO_IPFETCH` address is working correclty (if unset default value is chosen).
+- Make sure `NEKO_NAT1TO1` is blank and `NEKO_IPFETCH` address is working correctly (if unset default value is chosen).
 - Test externally to confirm it works.
 - Internally you have to access it using `<your-public-ip>:port`
 
@@ -201,7 +201,7 @@ Check if your TCP port is exposed correctly and your reverse proxy is correctly
 Getting black screen with a cursor, but no browser.
 ```
 
-Most likely you forgot to add `-cap-add=SYS_ADMIN` when using chromium-based brwosers.
+Most likely you forgot to add `-cap-add=SYS_ADMIN` when using chromium-based browsers.
 
 ### Unrelated server errors