Fix links to headings

docs/fleet/rbac.md

@@ -14,7 +14,7 @@ Users can have access to different fleet management capabilities depending on wh
 - **Owner**: Can see and edit [every tab on the machine page](/fleet/machines/#navigating-the-machine-page).
   Can manage users in the app.
 - **Operator**: Can see and use only the [**CONTROL**](/fleet/machines/#control) tab.
-  Cannot see or edit the [**CONFIGURE**](/fleet/machines/#configuration), [**LOGS**](/fleet/machines/#logs), or **CONNECT** tabs.
+  Cannot see or edit the [**CONFIGURE**](/fleet/machines/#configure), [**LOGS**](/fleet/machines/#logs), or **CONNECT** tabs.
 
 For more detailed information on the permissions each role confers for different resources, see [Permissions](/fleet/rbac/#permissions).
 

docs/get-started/viam.md

@@ -70,7 +70,7 @@ For each component that makes up your machine:
 
 1. Add it to your machine by [choosing the component type](/build/configure/#components) (example: `camera`) and model (example: `webcam`).
 2. Test it with the visual [control tab](/fleet/machines/#control).
-3. See any problems with in-app [logs](/fleet/machines/#logs), review or roll back configuration [history](/fleet/machines/#history).
+3. See any problems with in-app [logs](/fleet/machines/#logs), review or roll back [configuration history](/fleet/machines/#configure).
 
 After configuring your machine's hardware, you can configure [high level functionality](/services/) the same way:
 

docs/internals/rdk.md

@@ -45,7 +45,7 @@ After start-up, `viam-server` manages:
 When you or your collaborators change the configuration of a machine in the Viam app, `viam-server` automatically synchronizes the configuration to your machine and updates the running resources within 15 seconds.
 This means you can add, modify, and remove a modular resource instance from a running machine.
 
-You can see configuration changes made by yourself or by your collaborators on the [History tab](/fleet/machines/#history).
+You can see configuration changes made by yourself or by your collaborators by selecting **History** on the right side of your machine part's card on the **CONFIGURE** tab.
 You can also revert to an earlier configuration from the History tab.
 
 ### Logging

static/include/program/authenticate.md

@@ -4,7 +4,7 @@ To authenticate yourself to your machine, you need
 
       <!-- we will be releasing the ability to create API keys across all types of resources and combinations soon (i.e an API key can have an authorization on a org, location, machine or any combination of all three). this is correct for now though but it will be changing shortly. -->
 
-   To authenticate, [use a machine part API key](/fleet/machines/#security) or [an API key](/fleet/cli/#authenticate) with access to the machine.
+   To authenticate, [use a machine part API key](/fleet/machines/#api-keys) or [an API key](/fleet/cli/#authenticate) with access to the machine.
    Copy and paste the API key ID and the API key into your environment variables or directly into the code:
 
    {{< tabs >}}