doc: doc publish on PR merge

Updated the workflow to publish doc on
every PR merge and minor doc fixes.

Signed-off-by: divya pillai <divya.pillai@nordicsemi.no>

Author: divipillai

.github/workflows/zoomin-publish.yml

@@ -1,7 +1,18 @@
 name: Publish documentation to Zoomin prod
 
 on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+    paths:
+      - docs
   workflow_dispatch:
+    push:
+    branches:
+      - main
 
 jobs:
   create-zoomin-bundle:

docs/common/location_services.md

@@ -6,23 +6,23 @@ The Asset Tracker uses [nRF Cloud's location services](https://docs.nordicsemi.c
 
 The following location methods are supported:
 
-* **GNSS (Global Navigation Satellite System)**
+* **GNSS (Global Navigation Satellite System):**
 
-   - Highest accuracy positioning.
-   - Best suited for outdoor use.
-   - Higher power consumption compared to other methods.
+    - Highest accuracy positioning.
+    - Best suited for outdoor use.
+    - Higher power consumption compared to other methods.
 
-* **Cellular**
+* **Cellular:**
 
-   - Uses cellular tower information for positioning.
-   - Works indoors.
-   - Lower power consumption than GNSS.
+    - Uses cellular tower information for positioning.
+    - Works indoors.
+    - Lower power consumption than GNSS.
 
-* **Wi-Fi**
+* **Wi-Fi:**
 
-   - Uses nearby Wi-Fi access points for positioning.
-   - Excellent for indoor positioning.
-   - Lower power consumption than GNSS.
+    - Uses nearby Wi-Fi access points for positioning.
+    - Excellent for indoor positioning.
+    - Lower power consumption than GNSS.
 
 ## Integration with nRF Cloud
 

docs/modules/environmental.md

@@ -54,6 +54,6 @@ The Environmental module can be configured using the following Kconfig options:
 
 For more details on Kconfig options, see the `Kconfig.environmental` file in the module's directory.
 
-## State
+## State machine
 
 The environmental module implements a very simple state machine with only one state, `STATE_RUNNING`.

docs/modules/location.md

@@ -75,6 +75,6 @@ Several Kconfig options in `Kconfig.location` control this module's behavior. Th
 
 For more details on these configurations, refer to `Kconfig.location`.
 
-## State diagram
+## State machine
 
-The following is a representation of the state machine implemented in `location.c`. The module uses a single state (**STATE_RUNNING**) with an entry function (`location_init()`) that initializes the location library and a run function that processes incoming messages.
+The state machine implemented in `location.c`. The module uses a single state (**STATE_RUNNING**) with an entry function (`location_init()`) that initializes the location library and a run function that processes incoming messages.

docs/modules/power.md

@@ -57,7 +57,7 @@ See the `Kconfig.power` file in the module's directory for more details on the a
 - The Power module uses `npm1300_charger` as specified by device tree.
 - The two UART devices `uart0_dev` and `uart1_dev` defined in device tree will be enabled or disabled based on VBUS events.
 
-## State diagram
+## State machine
 
 The Power module uses a minimal state machine with a single state, **STATE_RUNNING**. In this state, the module: