docs(ingestion): enhancement for issue 12468

Author: lu-xiaoshuang

docs/actions/README.md

@@ -47,7 +47,7 @@ Actions are configured using a YAML file, much in the same way DataHub ingestion
 
 With each component being independently pluggable and configurable. 
 
-```yml
+```yaml
 # 1. Required: Action Pipeline Name
 name: <action-pipeline-name>
 
@@ -92,7 +92,7 @@ datahub:
 
 An simple configuration file for a "Hello World" action, which simply prints all events it receives, is
 
-```yml
+```yaml
 # 1. Action Pipeline Name
 name: "hello_world"
 # 2. Event Source: Where to source event from.
@@ -109,7 +109,7 @@ action:
 
 We can modify this configuration further to filter for specific events, by adding a "filter" block.
 
-```yml
+```yaml
 # 1. Action Pipeline Name
 name: "hello_world"
 
@@ -140,7 +140,7 @@ action:
 To run a new Action, just use the `actions` CLI command
 
 ```
-datahub actions -c <config.yml>
+datahub actions -c <config.yaml>
 ```
  
 Once the Action is running, you will see
@@ -252,4 +252,4 @@ Check out the [original announcement](https://www.youtube.com/watch?v=7iwNxHgqxt
 
 ## License
 
-Apache 2.0
+Apache 2.0

docs/ui-ingestion.md

@@ -327,7 +327,7 @@ DNS name for the `datahub-gms` pod:
 ### I see 'N/A' when I try to run ingestion. What do I do?
 
 If you see 'N/A', and the ingestion run state never changes to 'Running', this may mean 
-that your executor (`datahub-actions`) container is down. 
+that your `datahub-ingestion` container (where `datahub actions -c <config-file>` lives, see also [actions](actions/README.md)) is down.
 
 This container is responsible for executing requests to run ingestion when they come in, either
 on demand on a particular schedule. You can verify the health of the container using `docker ps`. Moreover, you can inspect the container logs using by finding the container id