Cleanup

Author: npentrel

assets/operate/spa.png

@@ -182,7 +182,7 @@ If your HTML file loads other files, use relative paths to ensure your files are
 | `visibility` | string | **Required** | Must be `"public"`. |
 | `description` | string | **Required** | A description of your module and what it provides. |
 | `url` | string | Optional | The URL of the GitHub repository containing the source code of the module. |
-| `applications` | array | Optional | Objects that provide information about the [single page apps](/operate/reference/single-page-apps/) associated with the module. |
+| `applications` | array | Optional | Objects that provide information about the [apps](/operate/reference/single-page-apps/) associated with the module. |
 | `models` | array | Optional | Empty unless you are shipping the app alongside models. For information on how to add models, see [Integrate other hardware](/operate/get-started/other-hardware/). |
 
 {{% /expand%}}
@@ -232,11 +232,11 @@ For subsequent updates run these commands again with an updated version number.
 {{% /tablestep %}}
 {{< /table >}}
 
-## Accessing your Single Page App
+## Accessing your app
 
 After uploading your module with the application configuration, your application will be available at:
 
-```
+```txt
 https://your-app-name_your-public-namespace.viamapplications.com
 ```
 
@@ -256,7 +256,7 @@ For a React app that shows Camera feeds for a machine, see [Viam Camera Viewer](
 
 ## Limitations
 
-- Single page apps currently only support single-machine applications
+- Apps currently only support single-machine applications
 - All modules with apps must have public visibility
 - There is no separate deploy step; the page will always render the latest version
 - Browsers with cookies disabled are not supported
@@ -266,4 +266,4 @@ For a React app that shows Camera feeds for a machine, see [Viam Camera Viewer](
 - Customer apps are stored publicly available on the internet
 - Avoid uploading sensitive information in your application code or assets
 - API keys and secrets are stored in the browser's localStorage or sessionStorage
-- Single page apps authenticate users with FusionAuth
+- Authenticate users with FusionAuth

docs/operate/control/single-page-apps.md

@@ -1020,7 +1020,7 @@ Do not change the <code>module_id</code>.</p>
 <td><code>applications</code></td>
 <td>array</td>
 <td>Optional</td>
-<td>Objects that provide information about the [Single Page Apps](/operate/reference/single-page-apps/) associated with the module.</td>
+<td>Objects that provide information about the [apps](/operate/reference/single-page-apps/) associated with the module.</td>
 </tr>
 
 </table>

docs/operate/get-started/other-hardware/_index.md

@@ -108,13 +108,13 @@ Application names have the following requirements:
 The URL for accessing your single page app will contain your application name:
 
 ```txt
-https://app-name.your-public-namespace.viamapps.com
+https://app-name_your-public-namespace.viamapps.com
 ```
 
 For example, if your organization namespace is `acme` and your application name is `dashboard`, your application will be accessible at:
 
-```
-https://dashboard.acme.viamapps.com
+```txt
+https://dashboard_acme.viamapps.com
 ```
 
 For more information about Single Page Apps, see the [Single Page Apps documentation](/operate/reference/single-page-apps/).

docs/operate/reference/naming-modules.md

@@ -192,7 +192,7 @@ Once you understand how to configure machines and use fragments, you can use [Pr
 #### Configure the sensor
 
 1. Navigate to the **CONFIGURE** tab of the machine details page in the [Viam app](https://app.viam.com) for your first machine.
-2. Click the **+** (Create) button and click **Component** from the dropdown.
+2. Click the **+** (Create) button and click **Component or service** from the dropdown.
    Click **sensor**, then search for `sds011` and click **sds001:v1** from the results.
 3. Click **Add module**.
    This adds the {{< glossary_tooltip term_id="module" text="module" >}} that provides the sensor model that supports the specific hardware we are using for this tutorial.
@@ -240,7 +240,7 @@ Once you configure the rest of your sensing machines, you'll be able to remotely
 
 Configure data capture and sync as follows:
 
-1. Click the **+** (Create) button and click **Service** from the dropdown.
+1. Click the **+** (Create) button and click **Component or service** from the dropdown.
 2. Click **data management**.
 3. Give your data manager a name such as the auto-populated name `data_manager-1` and click **Create**.
 4. Toggle **Syncing** to the on position.

docs/tutorials/control/air-quality-fleet.md

@@ -57,7 +57,7 @@
   [plugins.inputs]
 
   # change this key to a new one any time you need to restart from scratch
-  cacheKey = ["May022025"]
+  cacheKey = ["May272025"]
   # either "warn" or "error"
   failBuildOnError = true