Change spelling of dropdown (#2233)

Author: npentrel

.github/vale/styles/Viam/AvoidWithSubstitutionViam.yml

@@ -1,19 +1,18 @@
 extends: substitution
 message: "Consider if '%s' makes sense instead of '%s'."
 link: 'https://docs.google.com/document/d/1-SAcVPWcZHM1Na88d0_k5HVmc3tRtRHgmrXzKD3uF2I/edit'
-level: suggestion
+level: error
 ignorecase: true
 action:
   name: replace
 swap:
   in the website: on the website
   web app: Viam app or Viam platform
-  cloud app: Viam app or Viam platform
   user of an org: member of an org
   compute parts: Computer
   microprocessor: Raspberry Pi or Jetson or another specific term
   main part and child part: main part and sub-part
   main part and non-main part: main part and sub-part
   subpart: sub-part
-  on the app: in the app
-  Scuttlebot: SCUTTLE robot
+  drop down: dropdown
+  drop-down: dropdown

.github/vale/styles/Viam/AvoidWithSubstitutionViamsuggestonly.yml

@@ -0,0 +1,11 @@
+extends: substitution
+message: "Consider if '%s' makes sense instead of '%s'."
+link: 'https://docs.google.com/document/d/1-SAcVPWcZHM1Na88d0_k5HVmc3tRtRHgmrXzKD3uF2I/edit'
+level: suggestion
+ignorecase: true
+action:
+  name: replace
+swap:
+  cloud app: Viam app or Viam platform
+  Scuttlebot: SCUTTLE robot
+  on the app: in the app

.github/vale/styles/Viam/But.yml

@@ -2,7 +2,7 @@
 
 extends: existence
 message: "Do not start a paragraph with a 'but'."
-level: warning
+level: error
 scope: paragraph
 action:
   name: remove

.vale.ini

@@ -33,6 +33,7 @@ Viam.AvoidSubjunctive = YES
 Viam.AvoidSupported = YES
 Viam.AvoidWithSubstitution = YES
 Viam.AvoidWithSubstitutionViam = YES
+Viam.AvoidWithSubstitutionViamSuggestOnly = YES
 Viam.AvoidWithSubstitutionViamCaseSensitive = YES
 Viam.But = YES
 Viam.Careful = YES

docs/components/arm/ur5e.md

@@ -18,7 +18,7 @@ Click on the **Components** subtab and click **Create component**.
 Select the `arm` type, then select the `ur5e` model.
 Enter a name for your arm and click **Create**.
 
-![Web UI configuration panel for an arm of model ur5e in the Viam app, with Attributes & Depends On drop-downs and the option to add a frame.](/components/arm/ur5e-ui-config.png)
+![Web UI configuration panel for an arm of model ur5e in the Viam app, with Attributes & Depends On dropdowns and the option to add a frame.](/components/arm/ur5e-ui-config.png)
 
 Edit and fill in the attributes as applicable.
 

docs/components/arm/xarm6.md

@@ -19,7 +19,7 @@ Click on the **Components** subtab and click **Create component**.
 Select the `arm` type, then select the `xArm6` model.
 Enter a name for your arm and click **Create**.
 
-![Web UI configuration panel for an arm of model xArm6 in the Viam app, with Attributes & Depends On drop-downs and the option to add a frame.](/components/arm/xArm6-ui-config.png)
+![Web UI configuration panel for an arm of model xArm6 in the Viam app, with Attributes & Depends On dropdowns and the option to add a frame.](/components/arm/xArm6-ui-config.png)
 
 Edit and fill in the attributes as applicable.
 

docs/components/arm/xarm7.md

@@ -19,7 +19,7 @@ Click on the **Components** subtab and click **Create component**.
 Select the `arm` type, then select the `xArm7` model.
 Enter a name for your arm and click **Create**.
 
-![Web UI configuration panel for an arm of model xArm6 in the Viam app, with Attributes & Depends On drop-downs and the option to add a frame.](/components/arm/xArm7-ui-config.png)
+![Web UI configuration panel for an arm of model xArm6 in the Viam app, with Attributes & Depends On dropdowns and the option to add a frame.](/components/arm/xArm7-ui-config.png)
 
 Edit and fill in the attributes as applicable.
 

docs/components/arm/xarmlite.md

@@ -18,7 +18,7 @@ Click on the **Components** subtab and click **Create component**.
 Select the `arm` type, then select the `xArmLite` model.
 Enter a name for your arm and click **Create**.
 
-![Web UI configuration panel for an arm of model xArmLite in the Viam app, with Attributes & Depends On drop-downs and the option to add a frame.](/components/arm/xArmLite-ui-config.png)
+![Web UI configuration panel for an arm of model xArmLite in the Viam app, with Attributes & Depends On dropdowns and the option to add a frame.](/components/arm/xArmLite-ui-config.png)
 
 Copy and paste the following attribute template into your arm's **Attributes** box.
 Then remove and fill in the attributes as applicable to your arm, according to the table below.

docs/components/arm/yahboom-dofbot.md

@@ -24,7 +24,7 @@ Enter a name for your arm and click **Create**.
 
 There are no attributes available for this modular arm.
 
-![Web UI configuration panel for an arm of model yahboom-dofbot in the Viam app, with Attributes & Depends On drop-downs and the option to add a frame.](/components/arm/yahboom-dofbot-ui-config.png)
+![Web UI configuration panel for an arm of model yahboom-dofbot in the Viam app, with Attributes & Depends On dropdowns and the option to add a frame.](/components/arm/yahboom-dofbot-ui-config.png)
 
 Edit and fill in the attributes as applicable.
 

docs/components/base/wheeled.md

@@ -22,7 +22,7 @@ Click on the **Components** subtab and click **Create component**.
 Select the `base` type, then select the `wheeled` model.
 Enter a name for your arm and click **Create**.
 
-{{< imgproc src="/components/base/wheeled-base-ui-config.png" alt="An example configuration for a wheeled base in the Viam app config builder, with Attributes & Depends On drop-downs and the option to add a frame." resize="600x" >}}
+{{< imgproc src="/components/base/wheeled-base-ui-config.png" alt="An example configuration for a wheeled base in the Viam app config builder, with Attributes & Depends On dropdowns and the option to add a frame." resize="600x" >}}
 
 Select the motors attached to the base as your **Right Motors** and **Left Motors**.
 Edit and fill in the attributes as applicable.

docs/components/camera/webcam.md

@@ -23,7 +23,7 @@ Enter a name for your camera and click **Create**.
 {{< imgproc src="/components/camera/configure-webcam.png" alt="Configuration of a webcam camera in the Viam app config builder." resize="600x" >}}
 
 Edit and fill in the attributes as applicable.
-If you click on the **Video Path** field while your robot is live, a drop down autopopulates with identified camera paths.
+If you click on the **Video Path** field while your robot is live, a dropdown autopopulates with identified camera paths.
 
 {{% /tab %}}
 {{% tab name="JSON Template" %}}
@@ -139,7 +139,7 @@ Viam supports the following pixel formats:
 - YUY2
 - Z16
 
-If your machine is connected to the Viam app, the available pixel formats supported by your camera automatically appear in the **Format** drop down menu, which is visible when you click the **Show more** button.
+If your machine is connected to the Viam app, the available pixel formats supported by your camera automatically appear in the **Format** dropdown menu, which is visible when you click the **Show more** button.
 
 ## View the camera stream
 

docs/components/encoder/fake.md

@@ -54,7 +54,7 @@ No attributes are available for `fake` encoders.
 
 ## Test the encoder
 
-Once your encoder is configured and your robot is connected, go to the [**Control** tab](/manage/fleet/robots/#control) and click on the encoder's drop-down panel.
+Once your encoder is configured and your robot is connected, go to the [**Control** tab](/manage/fleet/robots/#control) and click on the encoder's dropdown panel.
 The ticks count is displayed.
 
 ![Encoder control panel.](/components/encoder/control.png)

docs/components/generic/_index.md

@@ -15,7 +15,7 @@ no_list: true
 The _generic_ component {{< glossary_tooltip term_id="subtype" text="subtype" >}} enables you to add support for unique types of hardware that do not already have an [appropriate API](/program/apis/#component-apis) defined for them.
 
 For example, when using an [arm component](/components/arm/), it makes sense to use the [arm API](/components/arm/#api), which provides specific functionality an arm component needs, such as moving to position or stopping movement.
-But if you want to use an LED display, you need very different functionality that isn't currently exposed in any API.
+If you want to use an LED display, you need very different functionality that isn't currently exposed in any API.
 Instead, you can use the generic component API to add support for your unique type of hardware, like LED displays, to your machine.
 
 There are no built-in generic component models (other than `fake`).

docs/components/input-controller/gamepad.md

@@ -77,7 +77,7 @@ If you have another controller that you want to use to control your robot, feel
 
 ## Troubleshooting
 
-- If you are not able to see a drop-down menu with the name of your controller appear in the **Control** tab, try specifying the `dev_file` attribute to match the exact path to your device.
+- If you are not able to see a dropdown menu with the name of your controller appear in the **Control** tab, try specifying the `dev_file` attribute to match the exact path to your device.
   You can also try setting `auto_reconnect` to `True`.
 
 You can find additional assistance in the [Troubleshooting section](/appendix/troubleshooting/).

docs/components/input-controller/mux.md

@@ -56,7 +56,7 @@ Then remove and fill in the attributes as applicable to your input controller, a
 {{% /tab %}}
 {{< /tabs >}}
 
-From the **Depends On** drop-down menu, select all of the source input controllers for your `mux` controller to combine.
+From the **Depends On** dropdown menu, select all of the source input controllers for your `mux` controller to combine.
 
 {{% /tab %}}
 {{% tab name="JSON Template" %}}

docs/components/motor/fake.md

@@ -108,7 +108,7 @@ The driver data sheet (for a real, not fake, motor) will specify which one to us
 
 ## Test the motor
 
-Once your motor is configured and your robot is connected, go to the [**Control** tab](/manage/fleet/robots/#control) and click on the motor's drop-down panel.
+Once your motor is configured and your robot is connected, go to the [**Control** tab](/manage/fleet/robots/#control) and click on the motor's dropdown panel.
 Use the buttons to try turning your motor forwards or backwards at different power levels and notice how the **Position** number changes.
 
 ![Motor control panel.](/components/motor/control.png)

docs/components/movement-sensor/viam-visual-odometry.md

@@ -51,7 +51,7 @@ Follow the instructions below to set up the `monocular-visual-odometry` module o
 1. Select the `camera` type, then select the `webcam` model.
 1. Enter a name for your camera, then click **Create**.
 1. In the resulting camera component configuration pane, select a **Video path** for your camera.
-   If your robot is live, the drop-down menu auto-populates any identified camera stream paths.
+   If your robot is live, the dropdown menu auto-populates any identified camera stream paths.
 1. Then, click **Create component** in the lower-left corner again.
 1. Select **Movement Sensor**, then select `visual_odometry:opencv_orb`.
    You can also search for "visual_odometry".

docs/manage/fleet/_index.md

@@ -56,9 +56,9 @@ Permissions are added at the organization level and apply to everything in an or
 - **Operator**: Can see and use only the [remote control tab](robots/#control).
   Cannot see or edit the [**Setup**](robots/#setup), [**Config**](robots/#configuration), [**History**](robots/#history), [**Logs**](robots/#logs), [**Code sample**](robots/#code-sample), or [**Security**](robots/#security) tabs.
 
-To view the roles each organization member has, click on the organization drop down in the top navigation bar and click on **Settings**.
+To view the roles each organization member has, click on the organization dropdown in the top navigation bar and click on **Settings**.
 
-If you have the **Owner** role, you can [invite new users](organizations/#invite-users-to-your-organization) and change the roles assigned to organization members using the role drop down for the respective user.
+If you have the **Owner** role, you can [invite new users](organizations/#invite-users-to-your-organization) and change the roles assigned to organization members using the role dropdown for the respective user.
 
 ![Example permissions overview](/manage/rbac.png)
 
@@ -98,7 +98,7 @@ You and your collaborators can deploy control logic, {{< glossary_tooltip term_i
 
 ### Remote control
 
-Everyone who has access to the robot can remotely control it on the app's [**Control** tab](robots/#control).
+Everyone who has access to the robot can remotely control it in the app's [**Control** tab](robots/#control).
 This allows you to visually test and remotely operate robot components and services.
 
 You can also control a robot using the [Viam mobile app](#the-viam-mobile-app).

docs/manage/fleet/locations.md

@@ -40,12 +40,12 @@ Click a location's name to display the list of robots associated with that locat
 To create a sub-location you must first create the sub-location as a location and then choose a parent location:
 
 1. Create a location and add at least one robot to it.
-2. At the bottom of the location's page, use the **New Parent Location** drop-down to choose a parent location.
+2. At the bottom of the location's page, use the **New Parent Location** dropdown to choose a parent location.
 3. Click **Change**.
 
 You can nest locations up to three levels deep.
 
-To move a sub-location to the top level of locations, select **Root** from the **New Parent Location** drop-down and then click **Change**.
+To move a sub-location to the top level of locations, select **Root** from the **New Parent Location** dropdown and then click **Change**.
 
 ### Share a location
 
@@ -56,9 +56,9 @@ You can share a location beyond its organization by [sharing a location with an
 
 #### Share a location with an additional organization
 
-Share your location with another organization you belong to by selecting the organization from the **Add Organization** drop-down menu and clicking **Share**.
+Share your location with another organization you belong to by selecting the organization from the **Add Organization** dropdown menu and clicking **Share**.
 
-![The Add Organization drop-down in the Viam app displays all organizations the user is a member of.](/manage/app-usage/add-org-drop-down.png)
+![The Add Organization dropdown in the Viam app displays all organizations the user is a member of.](/manage/app-usage/add-org-drop-down.png)
 
 The location's page lists newly added organization, along with the organization identified as the **primary owner**:
 
@@ -73,9 +73,9 @@ You can remove any organization except the primary owner from the shared list by
 
 Grant programmatic access to your location by sharing a location secret key.
 
-You can see the secret keys for a location in the **Location Secret Keys** drop-down:
+You can see the secret keys for a location in the **Location Secret Keys** dropdown:
 
-![The list of secret keys that can grant access to a location displays in the location secret keys drop down menu of the Viam app.](/manage/app-usage/location-secret-keys-drop-down.png)
+![The list of secret keys that can grant access to a location displays in the location secret keys dropdown menu of the Viam app.](/manage/app-usage/location-secret-keys-dropdown.png)
 
 {{< alert title="Caution" color="caution" >}}
 Do not share your location secret, part secret, or robot address publicly.

docs/manage/fleet/organizations.md

@@ -26,9 +26,9 @@ For example, you may have an account with one organization for your personal rob
 {{<youtube embed_url="https://www.youtube-nocookie.com/embed/eb7v6dabCGQ">}}
 
 You organization is shown in the upper right corner of [the Viam app](https://app.viam.com).
-If you click on the organization drop down, the app displays your name, email, and a list of organizations you belong to.
+If you click on the organization dropdown, the app displays your name, email, and a list of organizations you belong to.
 
-{{< imgproc alt="The org drop down showing an example user's name, email, Sign out button, list of organizations, and org settings button." src="/manage/app-usage/my-org.png" resize="400x" declaredimensions=true >}}
+{{< imgproc alt="The org dropdown showing an example user's name, email, Sign out button, list of organizations, and org settings button." src="/manage/app-usage/my-org.png" resize="400x" declaredimensions=true >}}
 
 If you used an email invite to sign up, you have two organizations to begin with: the organization that invited you and a personal organization for other projects.
 

docs/manage/fleet/robots.md

@@ -23,7 +23,7 @@ Click the name of a robot to go to that robot's page, where you'll find a variet
 
 ## Navigating the robot page
 
-The banner at the top of the robot page displays the robot's location, name, and a drop down list of all {{< glossary_tooltip term_id="part" text="parts" >}} of that robot.
+The banner at the top of the robot page displays the robot's location, name, and a dropdown list of all {{< glossary_tooltip term_id="part" text="parts" >}} of that robot.
 
 If you've connected your robot to a machine running `viam-server`, the banner also displays when the robot was last online, which version of `viam-server` it is running, the host name, the IP address or addresses, and its operating system.
 
@@ -106,7 +106,7 @@ Your robot and the Viam app communicate securely using [WebRTC](https://pkg.go.d
 
 The **Security** tab allows you to access, generate, and delete the **Robot part secret keys** and the **Robot part API keys** of your robot.
 
-![The Security tab of a robot`s page noting the Robot part API keys drop-down menu, with the clipboard icon on the far right and the Generate Key button underneath the drop-down.](/manage/app-usage/robot-secrets.png)
+![The Security tab of a robot`s page noting the Robot part API keys dropdown menu, with the clipboard icon on the far right and the Generate Key button underneath the dropdown.](/manage/app-usage/robot-secrets.png)
 
 You can copy a secret by clicking on the clipboard icon.
 

docs/manage/parts-and-remotes.md

@@ -38,9 +38,9 @@ You can make a multi-part robot by first configuring one part which is the "main
 The main part will be able to access the resources of its sub-parts.
 Sub-parts will _not_ have access to the resources of the main part.
 
-Use the parts drop-down menu in the top banner of your robot's page on the [Viam app](https://app.viam.com) to add a new sub-part:
+Use the parts dropdown menu in the top banner of your robot's page on the [Viam app](https://app.viam.com) to add a new sub-part:
 
-![The Viam app interface with the part drop-down open. A new part called 'my-sub-part' is being created.](/manage/parts-and-remotes/sub-part-config.png)
+![The Viam app interface with the part dropdown open. A new part called 'my-sub-part' is being created.](/manage/parts-and-remotes/sub-part-config.png)
 
 To delete a sub-part or make it the main part, use the buttons in the top right of the **Config** tab.
 

docs/program/debug.md

@@ -15,7 +15,7 @@ Read and filter a robot's logs to view updates from your robot's `viam-server` i
 
 Navigate to the **Logs** tab of your robot's page in [the Viam app](https://app.viam.com).
 
-Use the **Filter** input to filter the logs by key terms, and select from the **Levels** drop-down menu to filter the logs by warning level:
+Use the **Filter** input to filter the logs by key terms, and select from the **Levels** dropdown menu to filter the logs by warning level:
 
 ![Filtering by log level of info in the logs tab of the Viam app.](/program/sdks/log-level-info.png)