The Roku WebDriver is required to control an app. It can be used in conjunction with the Roku Robot Framework Library, Roku JavaScript library, another test framework, or a programming language or a programming language such as Python, Java, or Go to execute test cases.
+The Roku WebDriver is required to control an app. It can be used in conjunction with the Roku Robot Framework Library, Roku JavaScript library, another test framework, or a programming language or a programming language such as Python, Java, or Go to execute test cases.
Roku WebDriver APIs
Roku's WebDriver includes a set of Selenium-based REST APIs for sending commands to a Roku device. These APIs conform to the WebDriver standards specified by the World Wide Web Consortium (W3C). Specifically, the Roku WebDriver provides an HTTP-compliant JSON wire protocol with endpoints that map to their respective commands.
Path segments that are prefixed with a colon (:) represent variables. For example, the :sessionId variable is included in most command paths. This variable represents the ID of the session to be retrieved or the session where a command is to be sent.
contentId - {string} (optional): The contentId of the content to be played. You can include this parameter and the contentType to execute deep linking tests.
contentType - {string} (optional): The mediaType of the content to be played. You can include this parameter and the contentId to execute deep linking tests.
Example:
{
+channelId - {number}: The ID of the app to be launched.
contentId - {string} (optional): The contentId of the content to be played. You can include this parameter and the contentType to execute deep linking tests.
contentType - {string} (optional): The mediaType of the content to be played. You can include this parameter and the contentId to execute deep linking tests.
Example:
{
"channelId": "dev",
"contentId": "myMovie123",
"contentType": "movie"
@@ -704,7 +704,7 @@ next:
POST
session/:sessionId/launch
-channelId - {number}: The ID of the app to be launched.
contentId - {string} (optional): The contentId of the content to be played. You can include this parameter and the contentType to execute deep linking tests.
contentType - {string} (optional): The mediaType of the content to be played. You can include this parameter and the contentId to execute deep linking tests.
Example:
{
+channelId - {number}: The ID of the app to be launched.
contentId - {string} (optional): The contentId of the content to be played. You can include this parameter and the contentType to execute deep linking tests.
contentType - {string} (optional): The mediaType of the content to be played. You can include this parameter and the contentId to execute deep linking tests.
Example:
{
"channelId": "dev",
"contentId": "myMovie123",
"contentType": "movie"
@@ -1658,7 +1658,7 @@ next:
Testing production apps
-To test production apps with the Roku Web Driver APIs, package the app on your Roku device using the same Roku developer account linked to the production version of the app.
+To test production apps with the Roku Web Driver APIs, package the app on your Roku device using the same Roku developer account linked to the production version of the app.
`}
diff --git a/docs/DEVELOPER/discovery/continue-watching-cloud.md b/docs/DEVELOPER/discovery/continue-watching-cloud.md
index 9928ffb8..9b5a1ed0 100644
--- a/docs/DEVELOPER/discovery/continue-watching-cloud.md
+++ b/docs/DEVELOPER/discovery/continue-watching-cloud.md
@@ -267,7 +267,7 @@ curl --location --request GET 'https://apipub.roku.com/developer/v1/user-data/v1
### Update API
-To replace the list of content items in the Continue Watching row with a new list, send a **PUT** request to the Continue Watching API with a JSON body containing the same parameters listed in the [Add API section](https://developer.roku.com/docs/developer-program/discovery/continue-watching.md#add-api).
+To replace the list of content items in the Continue Watching row with a new list, send a **PUT** request to the Continue Watching API with a JSON body containing the same parameters listed in the [Add API section](https://developer.roku.com/docs/developer/discovery/continue-watching.md#add-api).
**Example (cURL):**
diff --git a/docs/DEVELOPER/discovery/continue-watching.md b/docs/DEVELOPER/discovery/continue-watching.md
index 7b83871b..8f031996 100644
--- a/docs/DEVELOPER/discovery/continue-watching.md
+++ b/docs/DEVELOPER/discovery/continue-watching.md
@@ -20,7 +20,7 @@ Continue Watching is a content category row within the **What to Watch** home sc
>
> **Certification requirement**:
>
-> * Apps in the U.S. Streaming Store that have streamed more than an average of 5 million hours per month over the last three months must participate in Roku’s Continue Watching program to pass [certification](/docs/developer-program/certification/certification.md#4-channel-operation).
+> * Apps in the U.S. Streaming Store that have streamed more than an average of 5 million hours per month over the last three months must participate in Roku’s Continue Watching program to pass [certification](/docs/developer/certification-overview/certification.md#4-app-operation).
> * Effective October 1st, 2026, apps outside the U.S. Streaming Store that have streamed more than an average of 1 million hours per month over the last three months must participate in Roku’s Continue Watching program.
> * This requirement also applies to new apps projected to reach the specified streaming hours threshold shortly after launch. TVOD, live linear, and made-for-kids apps are excluded from this requirement.
>
diff --git a/docs/DEVELOPER/getting-started/architecture/channel-manifest.md b/docs/DEVELOPER/getting-started/architecture/channel-manifest.md
index e0cc320d..027bc84d 100644
--- a/docs/DEVELOPER/getting-started/architecture/channel-manifest.md
+++ b/docs/DEVELOPER/getting-started/architecture/channel-manifest.md
@@ -138,7 +138,7 @@ The following categories of attributes are optional:
| `pause_aware` | integer | Attribute to specify the application responds to the pause remote control button event.
When this attribute is not set (the default), the application will not respond to the pause event and will toggle between "play" and "pause" modes when it receives the play event.
When the attribute is set to `1`, the play event strictly indicates play-mode (no toggling), and a pause event is necessary to invoke pause-mode. | `pause_aware=1` | |
| `channel_token` | | Token string used to grant access for specific Roku platform features (for example, Continue Watching) | `ewogICJpc3MiOiAidXJuOnJva3UuY29tOnRva2VubWludDpjaGFubmVsdG9rZW4iLAogICJhdWQiOiAidXJuOnJva3UuY29tOnN0Yi9jaGFubmVsIiwKICAic3ViIjogInVybjpyb2t1LmNvbTpzdGIvNzAzMDM0IiwKICAianRpIjogInVybjo4ZjNhN2FiNi1mMWJkLTQ1MTYtOTRiNS0wYTc3ZjNmMDY2OGEiLAogICJpYXQiOiAxNzA1NTI3NzE4LAogICJleHAiOiAyMDIwODg3NzE4LAogICJuYmYiOiAxNDU2NzkwNDAwLAogICJyb2t1LXRmdiI6ICIxIiwKICAicm9rdS1wZXJtIjogWwogICAgImp3dF9oZWFkZXIiCiAgXSwKICAicm9rdS1jaGFubmVsLWlkIjogWwogICAgIjEiCiAgXQp9` | |
| `run_as_process` | Integer | Required for integrating [Instant Resume](doc:instant-resume) and using the [chanperf debug command](doc:debugging), [Roku Resource Monitor](doc:resource-monitor), and [Perfetto](doc:app-tracing). | `run_as_process=1` | |
-| `rsg_version` | value | Sets the SceneGraph [observer callback model](doc:handling-application-events).
You must set this parameter to `rsg_version=1.3` by October 1, 2026, to continue passing [certification testing](doc:static-analysis-tool) . This version includes the [APIs for transferring node data that improve app performance](/docs/developer-program/performance-guide/data-transfer-apis.md)
If using [Roku OS 9.0](doc:release-notes#roku-os-9) or above, use `rsg_version=1.2`. This enables a new internal mechanism for processing component `