diff --git a/docs/getting-started/migrating/v14.md b/docs/getting-started/migrating/v14.md
index 4d2675cb5341..d3ba743f9fbc 100644
--- a/docs/getting-started/migrating/v14.md
+++ b/docs/getting-started/migrating/v14.md
@@ -125,6 +125,10 @@ public static from(raw: CCRaw, ctx: CCParsingContext): BinarySwitchCCSet {
 
 > [!NOTE]: Applications calling these methods can simply pass the driver instance.
 
+## Moved Serial API message implementations to `@zwave-js/serial` package
+
+All serial API message implementations have been moved to the `@zwave-js/serial` package. In addition to the main entry point, they are also available via `@zwave-js/serial/serialapi`.
+
 ## Other notable changes
 
 These are the only ones I found to break dependent projects.
diff --git a/docs/usage/custom.md b/docs/usage/custom.md
index 396290762d7a..4064dfbfa88d 100644
--- a/docs/usage/custom.md
+++ b/docs/usage/custom.md
@@ -8,7 +8,7 @@ The only downside is that you won't necessarily receive any responses that would
 Here's an example how to turn off the LED on a **Aeotec Gen 5 stick**.
 
 ```ts
-const turnLEDOff = new Message(driver, {
+const turnLEDOff = new Message({
 	type: MessageType.Request,
 	functionType: 0xf2,
 	payload: Buffer.from("5101000501", "hex"),
@@ -28,7 +28,7 @@ await driver.sendMessage(turnLEDOff, {
 This example sends an `Anti-theft Get` command (which is currently unsupported) to node 2:
 
 ```ts
-const cc = new CommandClass(driver, {
+const cc = new CommandClass({
 	nodeId: 2,
 	ccId: CommandClasses["Anti-theft"], // or 0x5d
 	ccCommand: 0x02,