Fix lint errors in other documents

Author: jkossak

README.md

@@ -48,9 +48,9 @@ distributed edges
 - [UI](https://github.com/open-edge-platform/orch-ui): The web user interface for the Edge Orchestrator, allowing the
 user to manage most of the features of the product in an intuitive, visual, manner without having to trigger a series
 of APIs individually.
-- [CLI](https://github.com/open-edge-platform/orch-cli): The command line interface for the Edge Orchestrator, allowing the
-user to manage most of the features of the product in an intuitive, text-based manner without having to trigger a series
-of APIs individually.
+- [CLI](https://github.com/open-edge-platform/orch-cli): The command line interface for the Edge Orchestrator,
+allowing the user to manage most of the features of the product in an intuitive,
+text-based manner without having to trigger a series of APIs individually.
 - [Observability](https://docs.openedgeplatform.intel.com/edge-manage-docs/main/developer_guide/observability/index.html):
 A modular observability stack that provides visibility into the health and performance of the system, including logging,
 reporting, alerts, and SRE data from Edge Orchestrator components and Edge Nodes.

design-proposals/app-orch-deploy-applications.md

@@ -197,7 +197,8 @@ like Profiles and Parameter Templates are lost.
   - Update the `Edit Deployment` page similar to the changes to `Create Deployment`
   - Update the `Deployments` list page to support linkage to both Apps and DP
 
-  - Update the `Application` page to have a deployment link and display the `is_deployed` field in both list and detail view.
+  - Update the `Application` page to have a deployment link and display the `is_deployed`
+  field in both list and detail view.
 
   - Update any status tables and dashboards as necessary to support these changes.
 

design-proposals/eim-nbapi-cli-decomposition.md

@@ -2,7 +2,7 @@
 
 Author(s) Edge Infrastructure Manager Team
 
-Last updated: 17/12/25
+Last updated: 18/12/25
 
 ## Abstract
 
@@ -350,8 +350,8 @@ only the commands supported by the currently deployed scenario.
 ### 3. Data Model Changes
 
 - Collaborate with teams/ADR owners to establish (per scenario):
-   - Required changes at Inventory level  
-   - Impact on APIs from these changes (changes in data models)
+  - Required changes at Inventory level  
+  - Impact on APIs from these changes (changes in data models)
 
 ## Summary of Current Requirements
 

design-proposals/eim-pxe-with-managed-emf.md

@@ -30,7 +30,8 @@ Given its small footprint it is possible to deploy PXE server on site using seve
 
 In this solution, the PXE server only stores the `ipxe.efi` binary (that is downloaded from the remote orchestrator),
 and serves it to local Edge Nodes attempting the PXE boot. During the PXE boot, ENs download `ipxe.efi` and boot into it.
-The iPXE script includes a logic to fetch IP address from a local DHCP server and download Micro-OS from the remote EMF orchestrator.
+The iPXE script includes a logic to fetch IP address from a local DHCP server and download Micro-OS
+from the remote EMF orchestrator.
 Once booted into Micro-OS, the provisioning process is taken over by the cloud-based orchestrator. From now on, ENs
 communicate with the remote EMF orchestrator to complete OS provisioning.
 The secure channel is ensured by using HTTPS communication with JWT authorization.

design-proposals/platform-installer-simplification.md

@@ -449,9 +449,9 @@ deployment is delayed.
 
 #### Eliminate ArgoCD
 
-Once the syncwaves have been reduced or eliminated, then it is feasible to eliminate ArgoCD in favor of a simpler tool. We
-will explore alternatives such as umbrella charts, the helmfile tool, or other opensource solutions. We may explore repo
-and/or chart consolidation to make the helm chart structure simpler.
+Once the syncwaves have been reduced or eliminated, then it is feasible to eliminate ArgoCD in favor of a
+simpler tool. We will explore alternatives such as umbrella charts, the helmfile tool, or other opensource
+solutions. We may explore repo and/or chart consolidation to make the helm chart structure simpler.
 
 Eliminating argocd will allow the following pods to be eliminated from the platform:
 

design-proposals/vpro-device.md

@@ -313,4 +313,5 @@ had access to DMT capabilities. This provided critical recovery mechanisms
 including the ability to remotely reboot the device if provisioning
 got stuck, access the device out-of-band for troubleshooting, and
 recover from provisioning failures without requiring physical access to the device.
-By moving activation to post-OS deployment, we lose all these recovery capabilities during the critical OS provisioning phase.
+By moving activation to post-OS deployment, we lose all these recovery capabilities during the critical
+OS provisioning phase.