update screenshot paths [netlify-build]

Author: pwseg

src/connections/auto-instrumentation/configuration.md

@@ -10,8 +10,8 @@ This guide details how to use signals, and their associated data, generated in o
 
 This guide assumes that you've already added the Signals SDK to your application. If you haven't yet, see the [Auto-Instrumentation Setup](/docs/connections/auto-instrumentation/) guide for initial setup.
 
-> info "Auto-Instrumentation Pilot"
-> Auto-Instrumentation is currently in pilot and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
+> info "Auto-Instrumentation Private Beta"
+> Auto-Instrumentation is currently in Private Beta and is governed by Segment's [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}. Segment is actively iterating on and improving the Auto-Instrumentation user experience.
 
 > success "Enable Auto-Instrumentation"
 > To enable Auto-Instrumentation in your Segment workspace, reach out to your dedicated account manager.                     

src/connections/auto-instrumentation/event-builder.md

@@ -12,9 +12,11 @@ You can use it to create Track, Identify, Page, and other event types directly f
 
 ## Access the Event Builder
 
-The Event Builder appears as a tab within each source, next to the Debugger. If you don't see the Event Builder tab, first confirm that you've installed the required Auto-Instrumentation SDK. If you've installed the SDK but still don't see the Event Builder tab, reach out to your Segment account manager to verify your workspace is included in the Auto-Instrumentation Private Beta.
+The Event Builder appears as a tab within each source, next to the Debugger. If you don't see the Event Builder tab, first confirm that you've installed the required Auto-Instrumentation SDK. 
 
-![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment source](images/autoinstrumentation_signals.png)
+If you've installed the SDK but still don't see the Event Builder tab, reach out to your Segment account manager to verify your workspace is included in the Auto-Instrumentation Private Beta.
+
+![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment source](images/event_builder_tab.png)
 
 > info "Event Builder during Private Beta"
 > During Private Beta beta, both the Event Builder and the legacy Auto-Instrumentation tab appear in the navigation. Segment will remove the legacy tab once all customers have migrated to the Event Builder experience.

src/connections/auto-instrumentation/web-setup.md

@@ -69,7 +69,7 @@ After integrating the SDK and running your app, verify that Segment is collectin
 
 1. In your Segment workspace, return to **Connections > Sources**, then select the Source you created for Auto-Instrumentation.
 2. In the Source header, look for the **Event Builder** tab. If the tab does not appear, make sure you’ve installed the SDK correctly and are triggering signal activity using the debug URL.
-    ![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment Source](/images/event-builder-tab.png)
+    ![The Event Builder tab shown in the navigation bar between Debugger and Schema in a Segment Source](images/event-builder-tab.png)
 3. Open the **Event Builder** and follow the on-screen instructions to trigger signal detection. You’ll need to open your app in a browser using the custom debug URL Segment provides (for example,`?segment_signals_debug=true`).
 4. Interact with your app to trigger signals: click buttons, navigate pages, or submit forms. Segment collects and displays these as signals in the Event Builder.
 5. From the signals list, click **Configure event** to define a new event based on one or more signals. After configuring the event, click **Publish event rules**.