From 08934d9094e28d621df4ba07476c8ac008bcb69d Mon Sep 17 00:00:00 2001 From: colin Date: Wed, 13 Dec 2023 17:46:42 +0000 Subject: [PATCH] washing my language. --- safelist.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/safelist.md b/safelist.md index 12d24b6..ccbfc16 100644 --- a/safelist.md +++ b/safelist.md @@ -4,11 +4,11 @@ 1. **Manufacturer Level**: - Contains general policies and information applicable to all devices from that manufacturer. - - Includes a `whitelist-ips.json` and `security-contact.json` relevant to the entire range of products. + - Includes a `safelist-ips.json` and `security-contact.json` relevant to the entire range of products. 2. **Device-Specific Level**: - Provides detailed, device-specific instructions and information. - - Contains its own `whitelist-ips.json`, `security-contact.json`, and `firewall-profile.json`. + - Contains its own `safelist-ips.json`, `security-contact.json`, and `firewall-profile.json`. - Device-specific information overrides manufacturer-level information when present. #### Example Structure @@ -27,7 +27,7 @@ #### Precedence Rules -- **Device-Specific Over Manufacturer-Level**: Routers and other network management tools should prioritize device-specific instructions and settings. If a device-specific `whitelist-ips.json` or `security-contact.json` exists, it should override the manufacturer-level files. +- **Device-Specific Over Manufacturer-Level**: Routers and other network management tools should prioritize device-specific instructions and settings. If a device-specific `safelist-ips.json` or `security-contact.json` exists, it should override the manufacturer-level files. #### Goals for Hierarchical Safelist and Contacts