From 4d5d040769d212dd83e6f76085eea21d789f6b3a Mon Sep 17 00:00:00 2001
From: David Luevano Alvarado <david@luevano.xyz>
Date: Tue, 20 Jun 2023 17:25:17 -0600
Subject: fix typo on manga entry, expand jellyfin entry

---
 src/blog/a/manga_server_with_komga.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'src/blog/a')

diff --git a/src/blog/a/manga_server_with_komga.md b/src/blog/a/manga_server_with_komga.md
index 52af3a9..7c60e3e 100644
--- a/src/blog/a/manga_server_with_komga.md
+++ b/src/blog/a/manga_server_with_komga.md
@@ -397,7 +397,7 @@ server {
 
 If it's going to be used as a subdir on another domain then just change the `location` with `/subdir` instead of `/`; be careful with the `proxy_pass` directive, it has to match what you configured at `/etc/komga.conf` for the `SERVER_SERVLET_CONTEXT_PATH` regardless of the `/subdir` you selected at `location`.
 
-## SSL certificate
+### SSL certificate
 
 If using a subdir then the same certificate for the subdomain/domain should work fine and no extra stuff is needed, else if following along me then we can create/extend the certificate by running:
 
@@ -411,7 +411,7 @@ That will automatically detect the new subdomain config and create/extend your e
 certbot --nginx -d domainname.com -d subdomain.domainname.com -d komga.domainname.com
 ```
 
-## Starting using Komga
+## Start using Komga
 
 We can now `start`/`enable` the `komga.service`:
 
-- 
cgit v1.2.3-70-g09d2