diff --git a/docs/sphinx/showcases/sense/build.rst b/docs/sphinx/showcases/sense/build.rst
index ecb5586..b2b5dcd 100644
--- a/docs/sphinx/showcases/sense/build.rst
+++ b/docs/sphinx/showcases/sense/build.rst
@@ -14,11 +14,6 @@
    .. tab-item:: VS Code
       :sync: vsc
 
-      .. admonition:: Known issue
-
-         Compile commands generation is not working.
-         See :bug:`419310666` for updates.
-
       #. In **Bazel Targets** right-click the **//apps/blinky** folder
          and select **Build Package Recursively**.
 
diff --git a/docs/sphinx/showcases/sense/code_intelligence.rst b/docs/sphinx/showcases/sense/code_intelligence.rst
index 039dc59..88551e7 100644
--- a/docs/sphinx/showcases/sense/code_intelligence.rst
+++ b/docs/sphinx/showcases/sense/code_intelligence.rst
@@ -41,24 +41,27 @@
 
             You can also select code analysis targets from the bottom-left
             of your VS Code GUI, in the status bar. In the next image,
-            the mouse cursor (bottom-left of image) is hovering over the GUI element
-            for selecting code analysis targets.
+            the mouse cursor (bottom-left of image) is hovering over the GUI
+            element for selecting code analysis targets.
 
             .. figure:: https://storage.googleapis.com/pigweed-media/sense/20240802/select_target_status_bar.png
 
-      #. Select the ``rp2040`` option.
+      #. Select the ``rp2040-fastbuild`` option.
 
          The code intelligence is now set up to help you with physical Pico 1
          programming. The RP2040 is the microprocessor that powers the Pico 1.
-         If you had selected the other option, ``host_simulator``,
+         If you had selected the ``k8-fastbuild`` option,
          the code intelligence would be set up to help with programming the
          simulated app that you will run on your development host later.
-         Code intelligence for the Pico 2 (``rp2350``) isn't supported yet.
-         ``rp2040`` represents one platform, ``host_simulator`` another.
+         ``rp2040-fastbuild`` represents one platform, ``k8-fastbuild`` another.
 
-         We will verify the platform-specific code intelligence now by making sure
-         that :ref:`module-pw_log` invocations resolve to different backends. This
-         will make more sense after you do the hands-on demonstration.
+         We will verify the platform-specific code intelligence now by making
+         sure that :ref:`module-pw_log` invocations resolve to different
+         backends.
+
+         .. note::
+
+            Code intelligence for the Pico 2 (``rp2350``) isn't supported yet.
 
       #. Open ``//apps/blinky/main.cc``.
 
@@ -108,10 +111,10 @@
 
             #define PW_HANDLE_LOG PW_LOG_TOKENIZED_TO_GLOBAL_HANDLER_WITH_PAYLOAD
 
-      #. Open the Command Palette, switch your target to ``host_simulator``,
+      #. Open the Command Palette, switch your target to ``k8-fastbuild``,
          and then repeat this workflow again, starting from the ``PW_LOG_INFO``
-         invocation in ``//apps/blinky/main.cc``. You should see the definitions finally
-         resolve to a :ref:`module-pw_log_string` backend header.
+         invocation in ``//apps/blinky/main.cc``. You should see the definitions
+         finally resolve to a :ref:`module-pw_log_string` backend header.
 
    .. tab-item:: CLI
       :sync: cli
@@ -123,16 +126,17 @@
 -----------
 Explanation
 -----------
-When you set your platform to ``rp2040`` and followed the call to
+When you set your platform to ``rp2040-fastbuild`` and followed the call to
 ``PW_LOG_INFO()`` in ``//apps/blinky/main.cc`` back to its source,
 you ended on a header within ``pw_log_tokenized``. When you repeated
-the process a second time with the ``host_simulator`` platform you
+the process a second time with the ``k8-fastbuild`` platform you
 ended on a header in a different module, ``pw_log_string``. This proves
 that intelligent code navigation is working. The ``pw_log`` API is a
 :ref:`facade <docs-facades>`. It's implementation is swapped out during
-compilation depending on what platform you're building for. The ``rp2040``
-platform has been set up to use the ``pw_log_tokenized`` implementation, whereas
-the ``host_simulator`` platform uses the ``pw_log_string`` implementation.
+compilation depending on what platform you're building for. The
+``rp2040-fastbuild`` platform has been set up to use the ``pw_log_tokenized``
+implementation, whereas the ``k8-fastbuild`` platform uses the ``pw_log_string``
+implementation.
 
 Here's a diagram summary of how the intelligent code navigation resolved to
 different files depending on the code analysis target you selected:
@@ -142,8 +146,8 @@
    flowchart LR
 
      a["main.cc"] --> b["log.h"]
-     b["log.h"] -. rp2040 .-> c["pw_log_tokenized/.../log_backend.h"]
-     b["log.h"] -. host_simulator .-> d["pw_log_string/.../log_backend.h"]
+     b["log.h"] -. rp2040-fastbuild .-> c["pw_log_tokenized/.../log_backend.h"]
+     b["log.h"] -. k8-fastbuild .-> d["pw_log_string/.../log_backend.h"]
 
 .. _showcase-sense-tutorial-intel-summary:
 
diff --git a/docs/sphinx/showcases/sense/device_tests.rst b/docs/sphinx/showcases/sense/device_tests.rst
index ee3d05a..98a728e 100644
--- a/docs/sphinx/showcases/sense/device_tests.rst
+++ b/docs/sphinx/showcases/sense/device_tests.rst
@@ -18,12 +18,6 @@
    setup <showcase-sense-tutorial-hardware>` and must be
    run over a terminal.
 
-.. note::
-
-   This section requires the VS Code terminal because there's currently
-   no way to run wildcard tests from the **Bazel Targets** UI.
-   Wildcard tests will be explained more in a moment.
-
 .. _showcase-sense-tutorial-devicetests-setup:
 
 --------------------
@@ -65,6 +59,12 @@
                kayce@kayce0:~/tmp/sense$ export PATH="/home/kayce/.vscode/extensions/pigweed.pigweed-1.3.3/node_modules/@bazel/bazelisk:${PATH}"
                kayce@kayce0:~/tmp/sense$
 
+            .. note::
+
+               This section requires the VS Code terminal because there's currently
+               no way to run wildcard tests from the **Bazel Targets** UI.
+               Wildcard tests will be explained more in a moment.
+
       .. tab-item:: CLI
          :sync: cli
 
@@ -174,6 +174,10 @@
 #. Go to the terminal that the test runner is running in and press
    :kbd:`Control+C` to close it.
 
+.. note::
+
+   A few tests may fail. We're working on it!
+
 .. _showcase-sense-tutorial-devicetests-flash:
 
 -----------------------------------------
diff --git a/docs/sphinx/showcases/sense/host_tests.rst b/docs/sphinx/showcases/sense/host_tests.rst
index d61f334..36ab6ff 100644
--- a/docs/sphinx/showcases/sense/host_tests.rst
+++ b/docs/sphinx/showcases/sense/host_tests.rst
@@ -42,7 +42,7 @@
       .. tab-item:: VS Code
          :sync: vsc
 
-         Make sure that your platform is set to **host_simulator**, as demonstrated
+         Make sure that your platform is set to **k8-fastbuild**, as demonstrated
          in :ref:`showcase-sense-tutorial-intel-nav`. If VS Code was displaying
          red squiggly line warnings in ``blinky_test.cc``, those should go away.
 
diff --git a/docs/sphinx/showcases/sense/outro.rst b/docs/sphinx/showcases/sense/outro.rst
index 35109f8..9ea88f3 100644
--- a/docs/sphinx/showcases/sense/outro.rst
+++ b/docs/sphinx/showcases/sense/outro.rst
@@ -16,7 +16,17 @@
 ==========
 If you've got any questions or comments about Sense or Pigweed in
 general, or just want to say "hi", you can talk to the Pigweed team on our
-`Discord <https://discord.gg/M9NSeTA>`_.
+`Discord <https://discord.gg/M9NSeTA>`_. Or, drop into our monthly community
+meeting, Pigweed Live:
+
+.. grid:: 1
+
+   .. grid-item-card:: :octicon:`device-camera-video` Pigweed Live
+      :link: https://groups.google.com/g/pigweed
+      :link-type: url
+      :class-item: sales-pitch-cta-secondary
+
+      .. pigweed-live::
 
 Extend Sense with Pigweed's modules
 ===================================
diff --git a/docs/sphinx/showcases/sense/rpc.rst b/docs/sphinx/showcases/sense/rpc.rst
index e4d89512..d73e924 100644
--- a/docs/sphinx/showcases/sense/rpc.rst
+++ b/docs/sphinx/showcases/sense/rpc.rst
@@ -58,19 +58,19 @@
 
                   bazelisk run //apps/blinky:rp2350_console
 
-         If you see a selection prompt like the one below, select
-         **Debug Probe (CMSIS-DAP) - CDC-ACM UART Interface**.
+   If you see a selection prompt like the one below, select
+   **Debug Probe (CMSIS-DAP) - CDC-ACM UART Interface**.
 
-         .. code-block:: text
+   .. code-block:: text
 
-            Please select a serial port device.
-            Available ports:
-              1 - /dev/ttyACM0 - Raspberry Pi - Debug Probe (CMSIS-DAP) - CDC-ACM UART Interface
-              2 - /dev/ttyACM1 - Raspberry Pi - Pico - Board CDC
-              3 - /dev/ttyS0 - None - n/a
-              4 - /dev/ttyS1 - None - n/a
-              5 - /dev/ttyS2 - None - n/a
-              6 - /dev/ttyS3 - None - n/a
+      Please select a serial port device.
+      Available ports:
+        1 - /dev/ttyACM0 - Raspberry Pi - Debug Probe (CMSIS-DAP) - CDC-ACM UART Interface
+        2 - /dev/ttyACM1 - Raspberry Pi - Pico - Board CDC
+        3 - /dev/ttyS0 - None - n/a
+        4 - /dev/ttyS1 - None - n/a
+        5 - /dev/ttyS2 - None - n/a
+        6 - /dev/ttyS3 - None - n/a
 
 #. Toggle the Pico's LED by typing the following into **Python Repl** (the
    bottom-left pane) and then pressing :kbd:`Enter`:
diff --git a/docs/sphinx/showcases/sense/setup.rst b/docs/sphinx/showcases/sense/setup.rst
index c1c9adb..dc9b512 100644
--- a/docs/sphinx/showcases/sense/setup.rst
+++ b/docs/sphinx/showcases/sense/setup.rst
@@ -13,8 +13,17 @@
 ------------
 If you get stuck or confused at any point during the Sense tutorial, you're
 welcome (and encouraged!) to talk to the Pigweed team in our
-`Discord <https://discord.gg/M9NSeTA>`_ or
-`issue tracker <https://pwbug.dev>`_.
+`Discord <https://discord.gg/M9NSeTA>`_ or `issue tracker <https://pwbug.dev>`_.
+Or, drop into our monthly community meeting, Pigweed Live:
+
+.. grid:: 1
+
+   .. grid-item-card:: :octicon:`device-camera-video` Pigweed Live
+      :link: https://groups.google.com/g/pigweed
+      :link-type: url
+      :class-item: sales-pitch-cta-secondary
+
+      .. pigweed-live::
 
 .. _showcase-sense-tutorial-setup-prereqs:
 
@@ -31,11 +40,6 @@
 ------------------------
 Set up the Sense project
 ------------------------
-Usually, we recommend trying out the tutorial with Visual Studio Code (VS Code)
-but we're currently refactoring our VS Code extension and fixing some bugs
-(e.g. :bug:`419310666`). In the short-term, we recommend trying the CLI path of
-the tutorial, not the VS Code path.
-
 .. _Visual Studio Code: https://code.visualstudio.com/Download
 .. _Pigweed extension: https://marketplace.visualstudio.com/items?itemName=pigweed.pigweed-vscode
 .. _Extensions view: https://code.visualstudio.com/docs/editor/extension-marketplace#_browse-for-extensions
@@ -72,19 +76,6 @@
             you won't see the popups. That's OK; you can just skip the
             instructions for popups you didn't see.
 
-         .. admonition:: Troubleshooting
-
-            If you see a popup that says ``spawn bazel ENOENT``, try ignoring it
-            and proceeding with the rest of the tutorial. When the Bazel extension
-            for VS Code starts up, it tries to run queries right away, even though
-            the Bazel environment isn't completely ready yet. The Pigweed extension
-            for VS Code ensures that the Bazel environment sets up properly.
-
-            If the ``spawn bazel ENOENT`` popup seems like a legitimate error,
-            make sure that you have opened the correct folder i.e. directory.
-            If you're still seeing the issue after that, please
-            :ref:`ask the Pigweed team for help <showcase-sense-tutorial-setup-help>`.
-
       #. If you see the **Do you trust the authors of the files in this folder?** popup
          click **Yes, I trust the authors**.
 
@@ -106,7 +97,7 @@
 
       #. Open the **Extensions** pane (:kbd:`Control+Shift+X` on Linux and Windows,
          :kbd:`Command+Shift+X` on macOS), open the **Pigweed** extension, and make
-         sure that you're running version 1.9.1 or later. If not, click the **More actions** (**▼**)
+         sure that you're running version 1.9.9 or later. If not, click the **More actions** (**▼**)
          button next to **Uninstall**, then select **Install Specific Version**, and then select
          the latest version from the dropdown menu.