Documentation content post review update

Author: TaddyHC

content/hardware/04.pro/carriers/portenta-max-carrier/tutorials/mpcie-4g-modem/content.md

@@ -330,7 +330,7 @@ Once the overlays are set, please reboot the Portenta X8 to ensure the configura
 
 #### GNSS Global EG25 Module
 
-The **GNSS Global (EG25) Module** supports the QMI interface, making it compatible with **NetworkManager**. You can configure the modem using **nmcli** (NetworkManager’s command-line tool):
+The **GNSS Global (EG25) Module** supports the *Qualcomm MSM Interface (QMI)*, which is compatible with **NetworkManager**. You can configure the modem using **nmcli**, the command-line tool for **NetworkManager**:
 
 ```bash
 nmcli c add type gsm ifname cdc-wdm0 con-name wwan0 apn hologram connection.autoconnect yes
@@ -391,7 +391,7 @@ sudo systemctl stop ModemManager
 sudo systemctl disable ModemManager
 ```
 
-This allows **qmicli** to communicate directly with the QMI interface for modem operations.
+Once **ModemManager** has been disabled, you can use **qmicli** to communicate reliably with the QMI interface for modem operations.
 
 ***The **EC200A-EU** modem is not compatible with __QMI__. It requires raw AT commands over a USB serial interface. For more information, refer to the [Quectel EC200A-EU documentation](https://python.quectel.com/en/products/ec200a-eu).***
 
@@ -470,6 +470,10 @@ In a Docker environment, it is often useful to disable **ModemManager** to avoid
 sudo systemctl stop ModemManager
 ```
 
+```bash
+sudo systemctl disable ModemManager
+```
+
 For modem power management, the connection between the **PCIE Enable (GPIO5)** pin and **VCC (3V3)** pin is required for a proper power setup. This bridge ensures proper hardware functionality when controlling the modem power. Moreover, you should manage power through software to allow the modem to be rebooted in case it becomes unresponsive.
 
 Ensure that the Docker container has access to the GPIO device files by passing them into the container:

content/hardware/04.pro/carriers/portenta-mid-carrier/tutorials/user-manual/content.md

@@ -2168,7 +2168,7 @@ This step ensures the modem functions properly in QMI mode.
 
 The **ModemManager** service manages the power for the Pro 4G Module via a script. **Global (EG25)** and **EU (EC200A-EU)** modems are different and require different configurations:
 
-- **Global EG25 Module**: This modem is supported directly by **NetworkManager**, which works alongside **ModemManager**.
+- **Global EG25 Module**: This modem supports the *Qualcomm MSM Interface (QMI)*, making it compatible with **NetworkManager**, which uses **nmcli** as its command-line tool. It also works with **ModemManager** to manage modem connectivity.
 - **EU EC200A-EU Module**: This modem is **not officially supported** by **ModemManager**. It is **not QMI-compatible** and requires raw AT commands over a USB serial interface. It connects as a USB device, creating an `ec200aeu` network interface managed by existing `udev` rules. 
 
 Power management is handled by **ModemManager** using the following script setup. Before starting **ModemManager**, the system runs a script to power on the modem, and another script is run after the service stops to power off the modem:
@@ -2270,6 +2270,10 @@ In a Docker environment, it is often useful to disable **ModemManager** to avoid
 sudo systemctl stop ModemManager
 ```
 
+```bash
+sudo systemctl disable ModemManager
+```
+
 However, when **ModemManager** is active, it handles modem power automatically using customized scripts, such as:
 
 - `/usr/sbin/modem_on.sh`
@@ -2547,12 +2551,16 @@ The output will list the detected modems, including the Pro 4G Module. Note the
 
 ![Arduino Pro 4G Module - AT Commands](assets/portentaMIDcarrier_mpcie_4gmodem_at1.png)
 
-Before sending AT commands, ModemManager must be in debug mode. First, stop the ModemManager service using:
+Before sending AT commands, ModemManager must be in debug mode. First, stop and disable the ModemManager service using:
 
 ```bash
 sudo systemctl stop ModemManager
 ```
 
+```bash
+sudo systemctl disable ModemManager
+```
+
 Then start it in the background with debugging enabled by running:
 
 ```bash
@@ -2624,12 +2632,16 @@ This ensures the modem powers up correctly and becomes available for network ope
 
 #### Docker Container Considerations
 
-Disable ModemManager to prevent conflicts with tools like `qmicli` when managing either modem within a Docker container. This can be done by using the following command:
+Disable **ModemManager** to prevent conflicts with tools like `qmicli` when managing either modem within a Docker container. This can be done by using the following command:
 
 ```bash
 sudo systemctl stop ModemManager
 ```
 
+```bash
+sudo systemctl disable ModemManager
+```
+
 Inside the container, you will need to manage the modem’s power as explained in this [**EC200A-EU**](#emea-ec200a-eu-module-1) section.
 
 To send AT commands, use `qmicli` within the Docker container. For example, you might use following command to interact with the modem: