dasharo-binaries-paths-convention.md: Add more path examples

Signed-off-by: Filip Gołaś <[email protected]>

Author: philipanda

docs/kb/dasharo-binaries-paths-convention.md

@@ -23,10 +23,26 @@ where:
   `apu4`
 - `<framework>` - firmware framework, like `coreboot`, `slimbootloader`, `heads`
 - `[_payload]` - optional, firmware payload, like `_uefi`, `_heads`, `_seabios`
-- `<version>` - Dasharo version, like `v0.9.0`, `v1.7.2-rc1`
-
-Example, path to the v1.0.0 release binaries for Novacustom V540TU laptop:
-- `/novacustom/v540tu/coreboot_uefi/1.0.0/`
+- `<version>` - Dasharo version, like `v0.9.0`, `v1.7.2-rc1`, compliant with
+  the [versioning scheme](https://docs.dasharo.com/dev-proc/versioning/).
+
+Examples:
+- Dasharo (coreboot+Heads) Community Package for Novacustom V540TNx 14th
+  Gen laptops v1.0.0
+    + (historically kept in one path due to compatibility):
+    + `/novacustom/v540tnd/coreboot_heads/1.0.0/`
+    + `/novacustom/v540tne/coreboot_heads/1.0.0/`
+- Dasharo (coreboot+UEFI) Pro Package for Protectli V1000-series v0.9.3
+    + (historically kept in two directories, a common `protectli_vault_jsl`
+      path,
+    and in more specific variants like `protectli_vault_jsl_v1210` due to
+    temporal compatibility):
+    + `/protectli/v1210/coreboot_uefi/v0.9.3/`
+    + `/protectli/v1410/coreboot_uefi/v0.9.3/`
+    + `/protectli/v1610/coreboot_uefi/v0.9.3/`
+- Dasharo (coreboot+SeaBIOS) Community Package for PC Engines APU4 v24.08.00.01
+    + (unique versioning scheme)
+    + `/pcengines/apu4/coreboot_seabios/v24.08.00.01/`
 
 ### Motivation
 
@@ -46,8 +62,8 @@ framework/payload combination to reduce the ambiguity.
 It's argueable that a firmware framework without a payload makes little sense
 as it won't allow the device to boot. Dasharo Naming Convention allows for
 such cases though, so to reduce the risk of needing to come up with hacks like
-`none` payload and inconsistent lengths of th path to a binary, the `[_payload]`
-field is a part of the same directory name as the `<framework>`.
+`none` payload and inconsistent lengths of the path to a binary, the
+`[_payload]` field is a part of the same directory name as the `<framework>`.
 
 #### <vendor>/<model>