Fix link from content injection to uniqueid extension

src/content/collaboration/documents/content-injection.mdx

@@ -13,7 +13,7 @@ To inject content into documents server-side, use the PATCH endpoint described i
 The update document endpoint also allows JSON updates to modify documents on your Collaboration server, both On-Premises and Cloud:
 
 - Add `json`, `binary`, or `base64` content to any document server-side.
-- Inject content into specific nodes using the [UniqueID extension](/docs/editor/extensions/functionality/uniqueid).
+- Inject content into specific nodes using the [UniqueID extension](/editor/extensions/functionality/uniqueid).
 - Users can still collaborate in real-time as content is injected.
 - Track user and injected content changes, fully compatible with [document history](/collaboration/documents/history).
 
@@ -63,7 +63,7 @@ When updating via JSON, the server computes the difference between the current d
 To ensure precise updates, especially for node-specific changes, it is recommended to use the `nodeAttributeName` and `nodeAttributeValue` parameters. These can be generated by Tiptap's [UniqueID Extension](/editor/extensions/functionality/uniqueid) or a custom implementation.
 Note that this only works for top level nodes.
 
-- `nodeAttributeName`: Configured as `attributeName` in the [UniqueID extension](/docs/editor/extensions/functionality/uniqueid).
+- `nodeAttributeName`: Configured as `attributeName` in the [UniqueID extension](/editor/extensions/functionality/uniqueid).
 - `nodeAttributeValue`: The unique value generated for the node being updated. You can pass multiple values with `?nodeAttributeValue=a&=nodeAttributeValue=b`.
 
 You can use `?mode=append` to append nodes to the document's JSON representation without altering existing nodes.