Update location secret info

docs/manage/fleet/locations.md

@@ -52,10 +52,7 @@ To move a sub-location to the top level of locations, select **Root** from the *
 A location always belongs to the organization it was created in.
 Members of the organization have access to all locations in the organization by default.
 
-There are two ways to share a location beyond its organization:
-
-- [Share a location with an additional organization](#share-a-location-with-an-additional-organization)
-- [Share a location using location secret keys](#share-a-location-using-location-secret-keys)
+You can share a location beyond its organization by [sharing a location with an additional organization](#share-a-location-with-an-additional-organization).
 
 #### Share a location with an additional organization
 
@@ -71,15 +68,20 @@ The location's page lists newly added organization, along with the organization
 
 You can remove any organization except the primary owner from the shared list by clicking the **X** to the right of the location in the shared list.
 
-#### Share a location using api keys
+<!-- location keys are going away but no new solution yet
+#### Share a location using location secret keys
 
-Grant programmatic access to your location by sharing an api key.
+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:
 
 ![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)
 
-{{% snippet "secret-share.md" %}}
+{{< alert title="Caution" color="caution" >}}
+Do not share your location secret, part secret, or robot address publicly.
+Sharing this information could compromise your system security by allowing unauthorized access to your robot, or to the computer running your robot.
+{{< /alert >}}
+-->
 
 ##### Rotate a secret key
 

docs/modular-resources/examples/tflite-module.md

@@ -267,11 +267,9 @@ With everything configured and running, you can now run the inference client tha
 
 1. Then, run the following to start the inference client, providing the necessary access credentials and the path to the labels file extracted earlier:
 
-   TODO
-
    ```sh { class="command-line" data-prompt="$"}
    cd ~/example_workspace/opt/bin
-   ./example_audio_classification_client --model-label-path ~/example_workspace/yamnet_label_list.txt --robot-host my-robot-main.abcdefg123.viam.cloud --robot-api-key-secret abcdef1g23hi45jklm6nopqrstu7vwx8 --robot-api-key-id a1234b5c-678d-9012-3e45-67fabc8d9efa
+   ./example_audio_classification_client --model-label-path ~/example_workspace/yamnet_label_list.txt --robot-host my-robot-main.abcdefg123.viam.cloud --robot-api-key abcdef1g23hi45jklm6nopqrstu7vwx8 --robot-api-key-id a1234b5c-678d-9012-3e45-67fabc8d9efa
    ```
 
    The command should return output similar to:

static/include/snippet/show-secret.md

@@ -1,6 +1,6 @@
 {{< alert title="API key and API key id" color="info" >}}
-By default, the sample code does not include your robot API key and secret.
-We strongly recommend that you add your API key and secret as an environment variable and import this variable into your development environment as needed.
+By default, the sample code does not include your robot API key and API key id.
+We strongly recommend that you add your API key and API key id as an environment variable and import this variable into your development environment as needed.
 
 To show your robot's API key and API key id in the sample code, toggle **Include secret** on the **Code sample** tab.
 You can also see your API key and API key id on your robot's **Security** tab.