Simplify

Author: dandavison

docs/encyclopedia/activities/activities.mdx

@@ -43,5 +43,5 @@ back to the Temporal Service as part of the [ActivityTaskCompleted](/references/
 Event is added to the Workflow Execution's Event History. For other Activity-related Events, see
 [Activity Events](/workflow-execution/event#activity-events).
 
-If you only want to execute one Activity Function, then you don't need to use a Workflow: you can use your SDK Client to invoke it directly as a [Standalone Activity](/standalone-activity).
-This will have lower latency and will result in fewer [Billable Actions](/cloud/actions#actions-in-workflows) in Temporal Cloud.
+If you only want to execute one Activity Function, then you don't need to use a Workflow: you can
+use your SDK Client to invoke it directly as a [Standalone Activity](/standalone-activity).

docs/encyclopedia/activities/standalone-activity.mdx

@@ -19,8 +19,12 @@ tags:
 
 An [Activity Execution](/activity-execution) that is started directly by a [Client](/encyclopedia/temporal-sdks#temporal-client), without using a Workflow, is called a Standalone Activity.
 
-If you need to orchestrate multiple Activity Executions, then you should use a Workflow.
-But if you just need to execute a single Activity, then Standalone Activity will have lower latency and will result in fewer [Billable Actions](/cloud/actions) in Temporal Cloud.
+If you need to orchestrate multiple Activity Executions, then you should use a Workflow. But if you
+just need to execute a single Activity, then you can use a Standalone Activity. This will result in
+fewer [Billable Actions](/cloud/actions#actions-in-workflows) in Temporal Cloud. If your Activity
+Execution is short-lived, then you will also notice lower latency, since there are fewer worker
+round-trips than when executing the Activity in a Workflow.
 
-Standalone Activities support the same retry policies and timeouts as Workflow Activities, and you write your Activity Functions in the same way for both.
-In fact, an Activity Function can be executed both as a Standalone Activity and as a Workflow Activity.
+Standalone Activities support the same retry policies and timeouts as Workflow Activities, and you
+write your Activity Functions in the same way for both. In fact, an Activity Function can be
+executed both as a Standalone Activity and as a Workflow Activity.