Shorten manifest registry labels

Author: AnastaZIuk

README.md

@@ -74,7 +74,7 @@ At a high level this follows the same pattern used by mature package and artifac
 
 The same consumer module is also meant to stay reusable beyond Nabla itself.
 The default first-party registry is
-[`Devsh-Graphics-Programming/Nabla-Asset-Manifests`](https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests),
+[`Nabla-Asset-Manifests`](https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests),
 but consumers can point the module at a different manifest checkout and a
 different `GitHub Release` channel without changing the build-graph model.
 

cmake/README.md

@@ -68,7 +68,7 @@ nam_add_channel_target(
 
 For the official first-party Nabla registry you normally set `MANIFEST_ROOT`
 explicitly to a local checkout of
-`Devsh-Graphics-Programming/Nabla-Asset-Manifests`. The built-in
+[`Nabla-Asset-Manifests`](https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests). The built-in
 `MANIFEST_ROOT` default remains useful for repositories that colocate the
 module and their manifests in the same tree.
 
@@ -107,7 +107,7 @@ Current scope stays intentionally small:
   `MANIFEST_ROOT`
 - remote payload resolution still uses `GitHub Release assets` only
 - the default first-party Nabla registry stays
-  `Devsh-Graphics-Programming/Nabla-Asset-Manifests`
+  [`Nabla-Asset-Manifests`](https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests)
 - the built-in `MANIFEST_ROOT` default remains available for colocated
   module-plus-manifest repositories