update images to webp, update pre-commit hooks

content/posts/hosting-mumble-on-a-subdomain-with-nginx.md

@@ -4,7 +4,7 @@ date: 2024-01-04T10:04:57-07:00
 description: 'How to host a mumble server on a subdomain behind nginx reverse proxy'
 tags: ["nginx"]
 showTableOfContents: true
-image: "/images/nginx-mumble.png"
+image: "/images/nginx-mumble.webp"
 weight: 1
 type: "post"
 ---
@@ -13,7 +13,7 @@ type: "post"
 
 Well I couldn't find any actual examples of someone doing what I wanted, namely, hosting
 the murmur server on a subdomain on my machine behind an nginx proxy. I only have ports 80
-and 443 opened on my router, so I chose to recieve the mumble traffic to come in on port 443.
+and 443 opened on my router, so I chose to receive the mumble traffic to come in on port 443.
 Sounds easy enough, but the problem comes when you let nginx decrypt the packets in the process
 of passing them to the murmur server, it raises a TLS/SSL Termination Error. Murmur insists on
 End to End Encryption (E2EE), which is a good thing.
@@ -23,7 +23,7 @@ an Ad riddled page, here is the nginx config that got my setup working, all of t
 on an Arch Linux install, minus the `stream` block. Ports need to be defined for your setup for
 `INTERNAL_MUMBLE_PORT` (port that murmur is listening on) and `NEW_NGINX_SSL_PORT`. Previously,
 `NEW_NGINX_SSL_PORT` was 443, but the stream block now will be using 443, and you can't bind to the same
-port with seperate services. So pick a new port for the other ssl nginx services to listen on,
+port with separate services. So pick a new port for the other ssl nginx services to listen on,
 as well as pass traffic to, internally.
 
 `nginx.conf`