From 046820e03480ae8e11bcc960d319744e63c8ffb3 Mon Sep 17 00:00:00 2001
From: loredo <loredo@2b470e98-0d58-463d-a4d8-8e2adae1ed80>
Date: Mon, 18 Jan 2016 09:23:45 +0000
Subject: [PATCH] 98_GEOFANCY: fix link in commandref

git-svn-id: https://svn.fhem.de/fhem/trunk@10565 2b470e98-0d58-463d-a4d8-8e2adae1ed80
---
 fhem/FHEM/98_GEOFANCY.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fhem/FHEM/98_GEOFANCY.pm b/fhem/FHEM/98_GEOFANCY.pm
index 662ace72e..e6c2a2e85 100755
--- a/fhem/FHEM/98_GEOFANCY.pm
+++ b/fhem/FHEM/98_GEOFANCY.pm
@@ -657,7 +657,7 @@ sub GEOFANCY_ISO8601UTCtoLocal ($) {
           <br>
           You might also want to think about protecting the access by using HTTP Basic Authentication and encryption via TLS/SSL. Using TLS offloading in the reverse proxy software is highly recommended and software like HAproxy provides high control of data flow for TLS.<br>
           <br>
-          Also the definition of a dedicated FHEMWEB instance for that purpose together with <a href="#alllowed">allowed</a> might help to restrict FHEM's functionality (e.g. set attributes allowedCommands and allowedDevices to ",". Note that attributes <i>hiddengroup</i> and <i>hiddenroom</i> of FHEMWEB do NOT protect from just guessing/knowing the correct URI but would help tremendously to prevent easy inspection of your FHEM setup.)<br>
+          Also the definition of a dedicated FHEMWEB instance for that purpose together with <a href="#allowed">allowed</a> might help to restrict FHEM's functionality (e.g. set attributes allowedCommands and allowedDevices to ",". Note that attributes <i>hiddengroup</i> and <i>hiddenroom</i> of FHEMWEB do NOT protect from just guessing/knowing the correct URI but would help tremendously to prevent easy inspection of your FHEM setup.)<br>
           <br>
           To make that reverse proxy available from the internet, just forward the appropriate port via your internet router.<br>
           <br>