From 6a300d03a6766ac02f1d16dc4bf348bd03fe251e Mon Sep 17 00:00:00 2001
From: iraklis10 <1414477+iraklis10@users.noreply.github.com>
Date: Sun, 7 May 2023 19:35:02 +0100
Subject: [PATCH] Update local-instance.md

minor typo

Signed-off-by: iraklis10 <1414477+iraklis10@users.noreply.github.com>
---
 local-instance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/local-instance.md b/local-instance.md
index 515c6b3d..602e4b2b 100644
--- a/local-instance.md
+++ b/local-instance.md
@@ -6,7 +6,7 @@ The recommended way is the following:
 1. Set up your domain correctly to point to your home network
 1. Set up a reverse proxy by following the [reverse proxy documentation](./reverse-proxy.md) but only open port 80 (which is needed for the ACME challenge to work - however no real traffic will use this port).
 1. Set up a local DNS-server like a pi-hole and configure it to be your local DNS-server for the whole network. Then in the Pi-hole interface, add a custom DNS-record for your domain and overwrite the A-record (and possibly the AAAA-record, too) to point to the private ip-address of your reverse proxy (see https://github.com/nextcloud/all-in-one#how-can-i-access-nextcloud-locally)
-1. Enter the the ip-address of your local dns-server in the deamon.json file for docker so that you are sure that all docker containers use the correct local dns-server.
+1. Enter the ip-address of your local dns-server in the deamon.json file for docker so that you are sure that all docker containers use the correct local dns-server.
 1. Now, entering the domain in the AIO-interface should work as expected and should allow you to continue with the setup
 
 ## 2. Use the ACME DNS-challenge