Better context for file-based example (for now)

Signed-off-by: Benjamin Leggett <[email protected]>

SPEC.md

@@ -148,7 +148,7 @@ Plugins that consume any of these configuration keys should respect their intend
 Plugins may define additional fields that they accept and may generate an error if called with unknown fields. Runtimes must preserve unknown fields in plugin configuration objects when transforming for execution.
 
 #### Example configuration
-Network configuration with no inlined plugin confs, and two loaded plugin confs:
+The following is an example file-based JSON representation of a network configuration `dbnet` with no inlined plugin configurations, and two external aggregated plugin configurations (`bridge` and `tuning`) in JSON format:
 `/etc/cni/net.d/10-dbnet.conf`:
 ```jsonc
 {
@@ -195,7 +195,7 @@ Network configuration with no inlined plugin confs, and two loaded plugin confs:
 }
 ```
 
-Network configuration with one inlined plugin conf, and one loaded plugin conf:
+The following is an example file-based JSON representation of a network configuration `dbnet` with one inlined plugin configuration (`bridge`), and one external aggregated plugin configuration `tuning` in JSON format:
 `/etc/cni/net.d/10-dbnet.conf`:
 ```jsonc
 {
@@ -240,7 +240,7 @@ Network configuration with one inlined plugin conf, and one loaded plugin conf:
 }
 ```
 
-Network configuration with one inlined plugin conf, and no loaded plugin conf:
+The following is an example file-based JSON representation of a network configuration `dbnet` with one inlined plugin configuration (`bridge`), and no external aggregated plugin configs
 `/etc/cni/net.d/10-dbnet.conf`:
 ```jsonc
 {