From 2407a7a8cdc26bd8e267052f45e9f7f197c4618e Mon Sep 17 00:00:00 2001 From: TheNetworkGuy Date: Wed, 27 Dec 2023 15:36:33 +0100 Subject: [PATCH] Fixed typo in documentation --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0787581..c4c9e66 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ You can make the hostID field hidden or read-only to prevent human intervention. This is optional and there is a use case for leaving it read-write in the UI to manually change the ID. For example to re-run a sync. ### Template source -You can either use a Netbox device type custom field or Netbox config context for the Zabbix tempplate information. +You can either use a Netbox device type custom field or Netbox config context for the Zabbix template information. Using a custom field allows for only one template. You can assign multiple templates to one host using the config context source. Should you make use of an advanced templating structure with lots of nesting then i would recommend sticking to the custom field.