From 1a3073bdebad110cae20d2206d9c3a4394f4cbe8 Mon Sep 17 00:00:00 2001
From: arbadacarba <63317640+arbadacarbaYK@users.noreply.github.com>
Date: Sun, 23 Apr 2023 00:08:17 +0200
Subject: [PATCH] Updated LNbits Extensions (markdown)

---
 LNbits-Extensions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/LNbits-Extensions.md b/LNbits-Extensions.md
index fe2c150..51bac0b 100644
--- a/LNbits-Extensions.md
+++ b/LNbits-Extensions.md
@@ -13,7 +13,7 @@ Please note that any other extension you find on the wild west of the internet m
 
 ## Install Extensions
 
-The LNbits Admin UI lets you change LNbits settings via the LNbits frontend. It is disabled by default and the first time you set the enviroment variable ```LNBITS_ADMIN_UI=true``` in the .env the settings are initialized and saved to the database and will be used (as long the UI is enabled). You will find the .env file within your lnbits/ or lnbits/apps/data folder by extending the command to list files in your directory to  ```ls -a``` then open it with ```sudo nano lnbits.env```or whatever it is called in your implementation.  
+The LNbits Admin UI lets you change LNbits settings via the LNbits frontend. It is disabled by default and the first time you set the enviroment variable ```LNBITS_ADMIN_UI=true``` in the .env the settings are initialized and saved to the database and will be used (as long the UI is enabled). You will find the .env file within your lnbits/ or lnbits/apps/data folder by extending the command to list files in your directory with  ```ls -a``` then open it with ```sudo nano lnbits.env```or whatever it is called in your implementation.  
 
 On Citadel/Umbrel it is called docker-compose.yml.