From 005e033b4ae1bc9c44f96b86da6448f2a87eec1f Mon Sep 17 00:00:00 2001
From: Evolving The Future <66333723+EvTheFuture@users.noreply.github.com>
Date: Fri, 29 Jan 2021 23:04:57 +0100
Subject: [PATCH] Update presentation.md (#787)

Added clarification on how to set a specific port number for ingress web traffic.
---
 docs/add-ons/presentation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/add-ons/presentation.md b/docs/add-ons/presentation.md
index 3219ef21..b002725d 100644
--- a/docs/add-ons/presentation.md
+++ b/docs/add-ons/presentation.md
@@ -74,7 +74,7 @@ Ingress allow users to access the add-on web interface via the Home Assistant UI
 To add Ingress support, follow the following steps:
 
 - The add-on will need to provide the web interface on port `8099`. Make sure that the add-on accepts only connections from `172.30.32.2` on that port and that the connections are treated as authenticated.
-- Update add-on configuration and set `ingress: true`. Here it is also possible to configure the Ingress port (default 8099).
+- Update add-on configuration and set `ingress: true`. Here it is also possible to configure the Ingress port by using the option `ingress_port: PORT_NUMBER` (default 8099).
 - If you need to configure the application inside your add-on with the right path and port, query the add-on info API endpoint.
 - If the application doesn't support relative paths or you can't set a base url, you can use nginx filter to replace the URL with correct path. Ingress adds a request header `X-Ingress-Path` that can be used.