From 35e08d267ae528dc285c2bf616b078a56f3942d2 Mon Sep 17 00:00:00 2001
From: Mad Scientist <67949699+madscientist16@users.noreply.github.com>
Date: Mon, 28 Oct 2024 23:46:04 +0000
Subject: [PATCH] Change sudo nano to sudoedit (#1165)

---
 docs/general/installation/linux.md  | 2 +-
 docs/general/networking/fail2ban.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/general/installation/linux.md b/docs/general/installation/linux.md
index 66f097bec..fc3d638ad 100644
--- a/docs/general/installation/linux.md
+++ b/docs/general/installation/linux.md
@@ -384,7 +384,7 @@ sudo apt install -f
 Due to the number of command line options that must be passed on to the Jellyfin binary, it is easiest to create a small script to run Jellyfin.
 
 ```sh
-sudo nano jellyfin.sh
+sudoedit jellyfin.sh
 ```
 
 Then paste the following commands and modify as needed.
diff --git a/docs/general/networking/fail2ban.md b/docs/general/networking/fail2ban.md
index fbc8eb9c8..aa1efd171 100644
--- a/docs/general/networking/fail2ban.md
+++ b/docs/general/networking/fail2ban.md
@@ -21,7 +21,7 @@ Jellyfin produces logs that can be monitored by Fail2ban to prevent brute-force
 You need to create a jail for Fail2ban. If you're on Ubuntu and use nano as editor, run:
 
 ```bash
-sudo nano /etc/fail2ban/jail.d/jellyfin.local
+sudoedit /etc/fail2ban/jail.d/jellyfin.local
 ```
 
 Add this to the new file, replacing `/path_to_logs` with the path to the log files above, e.g. `/var/log/jellyfin/`:
@@ -57,7 +57,7 @@ Note:
 The filter contains a set of rules which Fail2ban will use to identify a failed authentication attempt. Create the filter by running:
 
 ```bash
-sudo nano /etc/fail2ban/filter.d/jellyfin.conf
+sudoedit /etc/fail2ban/filter.d/jellyfin.conf
 ```
 
 Paste: