address feedback from @lahsivjar

docs/en/observability/apm/act-on-data/index.asciidoc

@@ -11,10 +11,11 @@ more actionable with:
 * *Alerts and rules*: The APM UI allows you to define rules to detect complex
   conditions within your APM data and trigger built-in actions when those conditions are met.
   Read more about alerts and rules in the <<apm-alerts,Incident management section>>.
-* *Custom links*: Build URLs that contain relevant metadata from a specific
-  trace. For example, you can create a link that creates a new GitHub issue with context in the
-  auto-populated in the issue body. These links will be shown in the _Actions_ context menu in
-  selected areas of the APM UI (for example, by transaction details). Read more in <<apm-custom-links,Custom links>>.
+* *Custom links*: Build URLs that contain relevant metadata from a specific trace.
+  For example, you can create a link that will take you to a page where you can open a new GitHub issue
+  with context already auto-populated in the issue body.
+  These links will be shown in the _Actions_ context menu in selected areas of the APM UI (for example, by transaction details).
+  Read more in <<apm-custom-links,Custom links>>.
 
 :leveloffset: +1
 

docs/en/observability/apm/api/index.asciidoc

@@ -7,7 +7,7 @@ There are two kinds of APIs related to Elastic APM:
 |===
 | <<apm-app-api>>
 | {kib} APIs specific to working with the APM UI including updating configuration options,
-  upload real user monitoring (RUM) source maps, and add annotations, and more.
+  uploading real user monitoring (RUM) source maps, adding annotations, and more.
 | <<apm-api>>
 | APIs for working with APM Server.
   These are mainly intake APIs that accept data from APM agents and are used primarily by APM agent developers.