Fix wording in note and example title

Author: sivanel97

docs/actions-and-automations/create-self-service-experiences/create-self-service-experiences.md

@@ -167,9 +167,9 @@ The basic structure of a self-service action looks like this (see key descriptio
 
 For complete examples of self-service actions using GitHub as the backend, check out the [guides section](/guides?tags=GitHub&tags=Actions).
 
-## Tracking self-service actions
+## Track self-service actions
 
-To gain visibility into how your self-service actions are being used and their performance, you can set up tracking for action runs. This allows you to monitor execution patterns, track success rates, and maintain audit trails of who executed what actions and when.  
+To gain visibility into how your self-service actions are being used and their performance, you can set up tracking for action runs. This allows you to monitor execution patterns, track success rates, and maintain audit trails what actions were executed and when. 
 
 The following tracking system works by creating a dedicated blueprint for action runs and setting up an automation that captures execution details whenever a specific self-service action is triggered as well as an automation that updates the action run's status. This approach can give you a centralized view of all action executions in your software catalog.
 

docs/actions-and-automations/create-self-service-experiences/setup-the-backend/setup-the-backend.md

@@ -58,7 +58,7 @@ For example, say we have an action with one user input that is the user's name.
 ```
 
 :::info `.run` available values
-At invocation, `.run` contains only the run `id`.
+When the action is triggered, the `.run` object includes only the run `id`.
 :::
 
 You may have noticed that the example above also sends `{{ .run.id }}`. This is a unique identifier for each execution of the action, and can be used to interact with the action run in Port from your backend.  

docs/actions-and-automations/define-automations/setup-action.md

@@ -47,7 +47,7 @@ Here is an example for an automation payload:
 ```
 
 :::info `.run` available values
-At invocation, `.run` contains only the run `id`.
+When the automation is triggered, the `.run` object includes only the run `id`.
 :::
 
 You may have noticed that the example above also sends `{{ .run.id }}`. This is a unique identifier for each execution of the automation, and can be used to interact with the automation run in Port from your backend.