From 05218c255558257a5ac8ca67d3002aba1d64dd16 Mon Sep 17 00:00:00 2001 From: Kevin Gottsman Date: Fri, 3 Apr 2015 01:03:59 -0400 Subject: [PATCH] Fix page header to the proper platform --- source/components/device_tracker.nmap_scanner.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/components/device_tracker.nmap_scanner.markdown b/source/components/device_tracker.nmap_scanner.markdown index 59f2c94e4ec6..6e34b8f7cd15 100644 --- a/source/components/device_tracker.nmap_scanner.markdown +++ b/source/components/device_tracker.nmap_scanner.markdown @@ -1,7 +1,7 @@ --- layout: page -title: "OpenWRT support" -description: "Instructions how to integrate OpenWRT routers into Home Assistant." +title: "Nmap support" +description: "Instructions how to integrate Nmap into Home Assistant." date: 2015-03-23 19:59 sidebar: false comments: false @@ -9,7 +9,7 @@ sharing: true footer: true --- -As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using nmap. The IP addresses to scan can be specified in any format that nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`). +As an alternative to the router-based device tracking, it is possible to directly scan the network for devices by using Nmap. The IP addresses to scan can be specified in any format that Nmap understands, including the network-prefix notation (`192.168.1.1/24`) and the range notation (`192.168.1.1-255`). ``` # Example configuration.yaml entry