Update docs

Author: jpalm3r

docs/user-guide/network.qmd

@@ -261,6 +261,10 @@ network.to_dataframe(sel="WaterLevel").head()
 
 After construction, nodes are re-labelled as integers.  Use `find()` to go from original coordinates to the integer ID and `recall()` to go back.
 
+::: {.callout-tip}
+When creating `NodeObservation` objects for skill assessment you generally do **not** need to call `find()`.  You can pass the original string ID or a `(edge, distance)` tuple directly as `node=`, and `NetworkModelResult` will resolve it for you during matching.  See [Skill assessment workflow](#skill-assessment-workflow) for details.
+:::
+
 ```{python}
 # Look up a named node by its original id
 node_id = network.find(node="117")
@@ -309,6 +313,11 @@ mr
 
 `NodeObservation` accepts a file path directly; the observation name is taken from the filename.
 
+The `node=` argument can be specified in three ways, depending on what information you have at hand.
+
+#### Option A — integer node ID (direct)
+
+Pass the integer ID assigned by the `Network`.  This is the most explicit form:
 
 ```{python}
 obs_1 = ms.NodeObservation(path_to_sensor_data_1, node=network.find(node="78"))
@@ -318,6 +327,35 @@ cc = ms.match(obs=[obs_1, obs_2], mod=mr)
 cc.skill()
 ```
 
+#### Option B — original string alias
+
+Pass the original node identifier from the source format (e.g. the Res1D node name) as a plain string.  The `NetworkModelResult` resolves it to the correct integer ID at match time, so you never need to call `network.find()` yourself:
+
+```{python}
+obs_1 = ms.NodeObservation(path_to_sensor_data_1, node="78")
+obs_2 = ms.NodeObservation(path_to_sensor_data_2, node="46")
+
+cc = ms.match(obs=[obs_1, obs_2], mod=mr)
+cc.skill()
+```
+
+::: {.callout-note}
+Resolution happens inside `ms.match()`.  If the string is not found in the network's alias map a `ValueError` is raised with a clear message indicating which alias could not be resolved.
+:::
+
+#### Option C — breakpoint by `(edge, distance)` tuple
+
+When your observation sits at a chainage along a reach rather than at a named junction node, pass a `(edge_id, distance)` tuple.  The `NetworkModelResult` looks up the corresponding breakpoint at match time:
+
+```python
+obs_bp = ms.NodeObservation(path_to_sensor_data_1, node=("94l1", 21.285))
+
+cc = ms.match(obs=obs_bp, mod=mr)
+cc.skill()
+```
+
+The tuple form is equivalent to calling `network.find(edge="94l1", distance=21.285)` beforehand and is resolved during matching.
+
 ## Development
 
 ### Custom network formats