Update "More information..." to "Learn more" in all examples

Co-authored-by: hawkeyexl <[email protected]>

Author: Copilot

docs/get-started/create-your-first-test.md

@@ -12,7 +12,7 @@ A [test](/docs/get-started/tests) in Doc Detective is a series of steps, where e
 
 ## What does this test do?
 
-This test navigates to `https://example.com`, checks for the presence of the `<h1>` heading with the text `Example Domain`, and verifies that the `More information...` link is present. It then clicks the link and captures a screenshot of the resulting page.
+This test navigates to `https://example.com`, checks for the presence of the `<h1>` heading with the text `Example Domain`, and verifies that the `Learn more` link is present. It then clicks the link and captures a screenshot of the resulting page.
 
 ## Prerequisites
 
@@ -53,8 +53,8 @@ To create your first test, follow these steps:
              "find": "Example Domain"
            },
            {
-             "description": "Verify that the 'More information...' link is present and working",
-             "click": "More information..."
+             "description": "Verify that the 'Learn more' link is present and working",
+             "click": "Learn more"
            },
            {
              "description": "Capture a screenshot of the resulting page",
@@ -70,7 +70,7 @@ To create your first test, follow these steps:
 
    - [`goTo`](/docs/get-started/actions/goTo): Navigates to the specified URL, https://example.com, to start the test flow.
    - [`find`](/docs/get-started/actions/find): Locates elements on the page using CSS selectors such as HTML tags like `h1` or `a`, and validates their presence and text content.
-   - [`click`](/docs/get-started/actions/click): Clicks on the specified element, in this case, the `More information...` link.
+   - [`click`](/docs/get-started/actions/click): Clicks on the specified element, in this case, the `Learn more` link.
    - [`screenshot`](/docs/get-started/actions/screenshot): Captures a screenshot of the current page and saves it to the specified path.
 
 4. Save the file.
@@ -149,8 +149,8 @@ After running the test, you should see the results in your terminal, which Doc D
                 {
                   "result": "PASS",
                   "resultDescription": "Clicked element. Found element by text. Clicked element.",
-                  "description": "Verify that the 'More information...' link is present and working",
-                  "click": "More information...",
+                  "description": "Verify that the 'Learn more' link is present and working",
+                  "click": "Learn more",
                   "stepId": "d5851502-807f-4cb9-981c-338201278f29"
                 },
                 {

docs/get-started/installation.md

@@ -34,8 +34,8 @@ Downloading and running Doc Detective is straightforward. Follow these steps to
              "find": "Example Domain"
            },
            {
-             "description": "Verify that the 'More information...' link is present and working",
-             "click": "More information..."
+             "description": "Verify that the 'Learn more' link is present and working",
+             "click": "Learn more"
            },
            {
              "description": "Capture a screenshot of the resulting page",

docs/references/schemas/config.md

@@ -10,14 +10,14 @@ Field | Type | Description | Default
 $schema | string | Optional. JSON Schema for this object.<br/><br/>Accepted values: `https://raw.githubusercontent.com/doc-detective/common/refs/heads/main/dist/schemas/config_v3.schema.json` | 
 configId | string | Optional. Identifier for the configuration. | 
 configPath | string | ReadOnly. Path to the configuration file. | 
-input | one of:<br/>- string<br/>- array of string | Optional. Paths to test specifications and documentation source files. May be paths to specific files or to directories to scan for files. | `.`
+input | one of:<br/>- string<br/>- array of string | Optional. Path(s) to test specifications and documentation source files. May be paths to specific files or to directories to scan for files. | `.`
 output | string | Optional. Path of the directory in which to store the output of Doc Detective commands. If a file path is specified, Doc Detective attempts to honor the file name specified, but file path behavior is controlled by the configured reporters. | `.`
 recursive | boolean | Optional. If `true` searches `input`, `setup`, and `cleanup` paths recursively for test specifications and source files. | `true`
 relativePathBase | string | Optional. Whether paths should be interpreted as relative to the current working directory (`cwd`) or to the file in which they're specified (`file`).<br/><br/>Accepted values: `cwd`, `file` | `file`
 loadVariables | string | Optional. Load environment variables from the specified `.env` file. | 
 origin | string | Optional. Default protocol and domain to use for relative URLs. | 
-beforeAny | one of:<br/>- string<br/>- array of string | Optional. Paths to test specifications to perform before those specified by `input`. Useful for setting up testing environments. | 
-afterAll | one of:<br/>- string<br/>- array of string | Optional. Paths to test specifications to perform after those specified by `input`. Useful for cleaning up testing environments. | 
+beforeAny | one of:<br/>- string<br/>- array of string | Optional. Path(s) to test specifications to perform before those specified by `input`. Useful for setting up testing environments. | 
+afterAll | one of:<br/>- string<br/>- array of string | Optional. Path(s) to test specifications to perform after those specified by `input`. Useful for cleaning up testing environments. | 
 detectSteps | boolean | Optional. Whether or not to detect steps in input files based on defined markup. | `true`
 allowUnsafeSteps | boolean | Optional. Whether or not to run potentially unsafe steps, such as those that might modify files or system state. | 
 logLevel | string | Optional. Amount of detail to output when performing an operation.<br/><br/>Accepted values: `silent`, `error`, `warning`, `info`, `debug` | `info`