Updated all schema references

Author: hawkeyexl

docs/get-started/actions/checkLink.md

@@ -17,7 +17,7 @@ You can specify the target URL directly as a string, or use an object for more o
 - `origin`: (Optional) Protocol and domain prepended to `url` when `url` is a path. If omitted and `url` is a path, the global `origin` from the configuration file is used.
 - `statusCodes`: (Optional) A single integer or an array of integers representing acceptable HTTP status codes. If omitted, defaults to `[200, 301, 302, 307, 308]`.
 
-> For comprehensive options, see the [`checkLink`](/docs/references/schemas/checkLink) reference.
+> For comprehensive options, see the [`checkLink`](/docs/references/schemas/checklink) reference.
 
 ## Examples
 

docs/get-started/actions/goTo.md

@@ -18,7 +18,7 @@ You can specify the target URL directly as a string, or use an object for more o
   - `url`: (Required) The URL to navigate to. Can be a full URL, a path, or a variable reference.
   - `origin`: (Optional) Protocol and domain prepended to `url` when `url` is a path. Overrides the global `origin` if set.
 
-> For comprehensive options, see the [`goTo`](/docs/references/schemas/goTo) reference.
+> For comprehensive options, see the [`goTo`](/docs/references/schemas/goto) reference.
 
 ## Examples
 

docs/get-started/actions/httpRequest.md

@@ -33,11 +33,11 @@ You can specify a simple GET request using a string shorthand or use an object f
     - `useExample`: (Optional) Use example data from the OpenAPI spec (`request`, `response`, or `both`).
     - `exampleKey`: (Optional) Key of the specific example to use if multiple exist.
     *Note: Properties like `request.headers`, `request.parameters`, `request.body` can override values from the OpenAPI definition or example.*
-  - *Output Saving:* You can also save the response body using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`httpRequest`](/docs/references/schemas/httpRequest) reference for details.
+  - *Output Saving:* You can also save the response body using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`httpRequest`](/docs/references/schemas/httprequest) reference for details.
 
 **Setting Variables:** To capture parts of the response for later steps, use the step-level `variables` object. You can assign values based on the response using expressions like `$$response.body`, `$$response.headers`, `$$response.status`, etc. You can use dot notation for nested JSON fields (e.g., `$$response.body.user.id`).
 
-> For comprehensive options, see the [`httpRequest`](/docs/references/schemas/httpRequest) reference.
+> For comprehensive options, see the [`httpRequest`](/docs/references/schemas/httprequest) reference.
 
 ## Examples
 

docs/get-started/actions/loadVariables.md

@@ -13,7 +13,7 @@ The `loadVariables` action loads environment variables from a specified `.env` f
 
 > You can also load globally applicable variables using the `loadVariables` property in the configuration file. This makes them available across all tests.
 >
-> For comprehensive options, see the [`loadVariables`](/docs/references/schemas/loadVariables) reference.
+> For comprehensive options, see the [`loadVariables`](/docs/references/schemas/loadvariables) reference.
 
 ## Example
 

docs/get-started/actions/record.md

@@ -24,7 +24,7 @@ You can specify the recording action in several ways:
 
 **Stopping the Recording:** You *must* include a `stopRecord` step later in your test to finalize and save the video file.
 
-> For comprehensive options, see the [`record`](/docs/references/schemas/record) and [`stopRecord`](/docs/references/schemas/stopRecord) references.
+> For comprehensive options, see the [`record`](/docs/references/schemas/record) and [`stopRecord`](/docs/references/schemas/stoprecord) references.
 
 ## Examples
 

docs/get-started/actions/runCode.md

@@ -25,11 +25,11 @@ You must specify the `runCode` action using an object format with the following
   - `timeout`: (Optional) Maximum duration in milliseconds to wait for the code execution to complete.
   - `exitCodes`: (Optional) An array of acceptable exit codes. If the code execution's exit code is not in this list, the step fails (default: `[0]`).
   - `stdio`: (Optional) A string or regular expression to validate against the code's combined stdout and stderr. If the output doesn't match, the step fails. Regex must start and end with `/` (e.g., `/^hello world.*/`).
-  - *Output Saving:* You can also save the code's output using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`runCode`](/docs/references/schemas/runCode) reference for details.
+  - *Output Saving:* You can also save the code's output using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`runCode`](/docs/references/schemas/runcode) reference for details.
 
 **Setting Variables:** To capture output into variables for later steps, use the step-level `variables` object. You can assign values based on the code's output using expressions like `$$stdio.stdout`, `$$stdio.stderr`, or `$$exitCode`.
 
-> For comprehensive options, see the [`runCode`](/docs/references/schemas/runCode) reference.
+> For comprehensive options, see the [`runCode`](/docs/references/schemas/runcode) reference.
 
 ## Examples
 

docs/get-started/actions/runShell.md

@@ -23,11 +23,11 @@ You can specify the command directly as a string or use an object for more optio
   - `timeout`: (Optional) Maximum duration in milliseconds to wait for the command to complete.
   - `exitCodes`: (Optional) An array of acceptable exit codes. If the command's exit code is not in this list, the step fails (default: `[0]`).
   - `stdio`: (Optional) A string or regular expression to validate against the command's combined stdout and stderr. If the output doesn't match, the step fails. Regex must start and end with `/` (e.g., `/^hello world.*/`).
-  - *Output Saving:* You can also save the command's output using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`runShell`](/docs/references/schemas/runShell) reference for details.
+  - *Output Saving:* You can also save the command's output using `path`, `directory`, `maxVariation`, and `overwrite` properties. See the [`runShell`](/docs/references/schemas/runshell) reference for details.
 
 **Setting Variables:** To capture output into variables for later steps, use the step-level `variables` object. You can assign values based on the code's output using expressions like `$$stdio.stdout`, `$$stdio.stderr`, or `$$exitCode`.
 
-> For comprehensive options, see the [`runShell`](/docs/references/schemas/runShell) reference.
+> For comprehensive options, see the [`runShell`](/docs/references/schemas/runshell) reference.
 
 ## Examples
 

docs/get-started/actions/stopRecord.md

@@ -17,7 +17,7 @@ This action takes a simple boolean value:
 
 >Note: You must include a `stopRecord: true` step to finalize and save any recording started with the `record` action.
 >
-> For comprehensive options, see the [`stopRecord`](/docs/references/schemas/stopRecord) reference.
+> For comprehensive options, see the [`stopRecord`](/docs/references/schemas/stoprecord) reference.
 
 ## Example