Update docs

docs/config.rst

@@ -476,9 +476,10 @@ unique_id of the node) and global patterns.
 Rules:
 
  - if multiple node-specific entries reference the same unique_id, only the first will be in effect - all others will be ignored
- - if the **node** and **interfaces** or **model** attributes are specified and a node's unique_id is a match, but the topology information or model information are not, then the overall match will fail and the global patterns will not be considered
- - **model** can't be the only matching attributes, **node** or **interfaces** are mandatory to have a valid match
+ - if both the **node** and **interfaces** attributes are specified and a node's unique_id is a match, but the topology information is not, then the overall match will fail and the global patterns will not be considered
+ - if both the **model** and **interfaces** attributes are specified and a node's model is a match, but the topology information is not, then the overall match will fail and the global patterns will not be considered
  - if there is no matching node-specific pattern for a node's unique_id, then the server will attempt to match the node against the global patterns (in the order they are specified in ``neighbordb``)
+ - **node** and **model** are mutually exclusive and can't be specified in the same pattern
  - if a node-specific pattern matches, the server will automatically generate an open pattern in the node's folder. This pattern will match any device with at least one LLDP-capable neighbor.  Example: ``any: any:any``
 
 .. code-block:: yaml