Update JetBrains IDE plugin Live Debugger documentation (#29734)

* Change log probes to logpoints to be consistent with feature in Web UI

* Remove capture depth and other references to things that are behind a feature flag

* Fix Vale error

* Apply suggestions from code review

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>

---------

Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>

Author: jfree

content/en/developers/ide_plugins/idea/live_debugger.md

@@ -2,72 +2,72 @@
 title: Live Debugger
 type: documentation
 further_reading:
-- link: "/dynamic_instrumentation/"
+- link: "/tracing/live_debugger/"
   tag: "Documentation"
-  text: "Learn more about Dynamic Instrumentation"
+  text: "Learn more about Live Debugger"
 - link: "/integrations/guide/source-code-integration/"
   tag: "Documentation"
   text: "Learn about Source Code Integration."
 ---
 
 ## Overview
-The Live Debugger enables you to add temporary log statements to your runtime code to collect information for debugging. The log statements (also referred to as "log probes") are added dynamically, so there is no need to redeploy your code, allowing you to quickly resolve issues in a running system. You can edit or delete log probes at any time, and they automatically expire after 60 minutes.
+The Live Debugger enables you to add logpoints—auto-expiring, non-breaking breakpoints—to your runtime code to collect information for debugging. The logpoints are added dynamically, so there is no need to redeploy your code, allowing you to resolve issues in a running system. You can edit or delete logpoints at any time, and they automatically expire after 60 minutes.
 
 ## Live Debugger tab
-The **Live Debugger** in the Datadog tool window shows the defined log probes and the log output from these probes:
+The **Live Debugger** in the Datadog tool window shows the defined logpoints and their related output:
 
 {{< img src="/developers/ide_plugins/idea/live_debugger/tool-window-tab.png" alt="The Live Debugger tab" style="width:100%;" >}}
 
-The tree on the left shows all log probes created by the current user. Select a log probe to display the details for that probe, including log messages emitted during the past 24 hours. At the top-right of the panel, **View logs in Datadog** opens the [Log Explorer][2] in Datadog to show log events for the selected probe.
+The tree on the left shows all logpoints created by the current user. Select a logpoint to display its status and the log messages emitted during the past 24 hours. At the top-right of the panel, **View logs in Datadog** opens the [Log Explorer][2] in Datadog to show log events for the selected logpoint.
 
-To navigate to the source code location for a probe, right-click and select **Jump to Source**.
+To navigate to the source code location for a logpoint, right-click and select **Jump to Source**.
 
 ## Source editor
-In the source editor, an icon is shown in the gutter for any line that has a log probe defined:
+In the source editor, an icon is shown in the gutter for any line that has a logpoint defined:
 
 {{< img src="/developers/ide_plugins/idea/live_debugger/gutter-icon.png" alt="Gutter icon in the source editor" style="width:100%;" >}}
 
-Click the icon to open the Datadog tool window and select the log probe. Right-click the icon for options to enable, disable, edit, and delete the log probe. These actions are described in later sections.
+Click the icon to open the Datadog tool window and show the selected logpoint. Right-click the icon for options to enable, disable, edit, and delete the logpoint. These actions are described in later sections.
 
-## Managing log probes
+## Managing logpoints
 
-### Add a log probe
-To add a log probe, right-click on a line of code in the source editor and select **Add a Log to a Live Service**. A dialog appears where you can enter the service name, the environment, and the log message you would like to have emitted at runtime:
+### Add a logpoint
+To add a logpoint, right-click on a line of code in the source editor and select **Add a Log to a Live Service**. A dialog appears where you can enter the service name, the environment, the log message you would like to have emitted at runtime, and an optional logpoint condition expression:
 
-{{< img src="/developers/ide_plugins/idea/live_debugger/new-log-probe.png" alt="Add a new log probe" style="width:75%;" >}}
+{{< img src="/developers/ide_plugins/idea/live_debugger/new-logpoint.png" alt="Add a new log probe" style="width:75%;" >}}
 
-The log message field accepts a log template that contains descriptive text and variable references—see the [Dynamic Instrumentation expression language][3] documentation for details. The log message is generated using the runtime state immediately *prior* to the line of code being executed.  
+The log message field accepts a log template that contains descriptive text and variable references—see the [Dynamic Instrumentation expression language][3] documentation for details. The log message is generated using the runtime state immediately *prior* to the line of code being executed. If a condition is defined, log events are generated only when the condition evaluates to true.
 
-Log probes expire automatically after 60 minutes.
+Logpoints expire automatically after 60 minutes.
 
 #### Local and remote versions
-Notice that the remote code may be a different version compared to the source code in the IDE. The New Log Probe dialog displays the version of the code that is deployed remotely, if possible, so that you can see exactly where the log probe will be placed. This requires that your application or service is [tagged with Git information][4].
+Notice that the remote code may be a different version compared to the source code in the IDE. The New Logpoint dialog displays the version of the code that is deployed remotely, if possible, so that you can see exactly where the logpoint is being placed. This requires that your application or service is [tagged with Git information][4].
 
-<div class="alert alert-info"><b>Tip</b>: Checking out this revision locally shows you the same code in your IDE that is running remotely, which simplifies the live debugging experience. However, this is not required as the Datadog plugin maps local line numbers for log probes to remote line numbers based on Git commit information.</div>
+<div class="alert alert-info"><b>Tip</b>: Checking out this revision locally shows you the same code in your IDE that is running remotely, which simplifies the live debugging experience. However, this is not required as the Datadog plugin maps local line numbers for logpoints to remote line numbers based on Git commit information.</div>
 
-### Edit a log probe
-To modify the log message for a probe, right-click the log probe and select **Edit**:
+### Edit a logpoint
+To modify the log message for a logpoint, right-click the logpoint and select **Edit**:
 
-{{< img src="/developers/ide_plugins/idea/live_debugger/edit-log-probe.png" alt="Edit a log probe" style="width:75%;" >}}
+{{< img src="/developers/ide_plugins/idea/live_debugger/edit-logpoint.png" alt="Edit a log probe" style="width:75%;" >}}
 
-The service and environment cannot be changed by editing the log probe, only the log message. Changing the service or environment requires deleting the probe and creating a new one.
+You can update the log message and the (optional) logpoint condition. Changing the service or environment requires deleting the logpoint and creating a new one.
 
-**Note**: Applying changes to the log probe also extends the expiration time to 60 minutes.
+**Note**: Applying changes to the logpoint also extends the expiration time to 60 minutes.
 
-### Delete a log probe
-You can delete log probes by right-clicking the icon in the gutter of the source editor, or the entry in the tool window, and selecting **Delete** from the context menu.
+### Delete a logpoint
+You can delete logpoints by right-clicking the icon in the gutter of the source editor, or the entry in the tool window, and selecting **Delete** from the context menu.
 
-### Enable and disable a log probe
-You can enable or disable log probes by right-clicking and selecting the appropriate context menu item. The icon changes to indicate the current state of the log probe:
+### Enable and disable a logpoint
+You can enable or disable logpoints by right-clicking and selecting the appropriate context menu item. The icon changes to indicate the current state of the logpoint:
 
 | Icon         | Description       |
 |--------------|-------------------|
 | {{< img src="/developers/ide_plugins/idea/live_debugger/probeActive.svg.png" alt="Active icon" width="24px" >}}      | **Active**: Log events will be generated when the line of code is about to be executed.|
-| {{< img src="/developers/ide_plugins/idea/live_debugger/probeDisabled.svg.png" alt="Inactive icon" width="24px" >}}  | **Disabled**: The log probe is inactive, either because it automatically expired or the user disabled it manually. |
-| {{< img src="/developers/ide_plugins/idea/live_debugger/probeError.svg.png" alt="Error icon" width="24px" >}}        | **Error**: The log probe is not generating log events due to an error. |
-| {{< img src="/developers/ide_plugins/idea/live_debugger/probeWarning.svg.png" alt="Warning icon" width="24px" >}}    | **Warning**: The log probe may not be generating log events. |
+| {{< img src="/developers/ide_plugins/idea/live_debugger/probeDisabled.svg.png" alt="Inactive icon" width="24px" >}}  | **Disabled**: The logpoint is inactive, either because it automatically expired or the user disabled it manually. |
+| {{< img src="/developers/ide_plugins/idea/live_debugger/probeError.svg.png" alt="Error icon" width="24px" >}}        | **Error**: The logpoint is not generating log events due to an error. |
+| {{< img src="/developers/ide_plugins/idea/live_debugger/probeWarning.svg.png" alt="Warning icon" width="24px" >}}    | **Warning**: The logpoint may not be generating log events. |
 
-Disabling then re-enabling a log probe extends the expiry time of the probe to 60 minutes.
+Disabling then re-enabling a logpoint extends its expiry time to 60 minutes.
 
 ## Prerequisites
 The Live Debugger feature supports Java and Python and is subject to the same setup requirements as [Dynamic Instrumentation][1].