Fixing some syntax

Author: jeremi

docs/developer_guide/api_usage/dci_api.md

@@ -9,7 +9,7 @@ myst:
 # DCI API
 
 OpenSPP provides a RESTful API that adheres to the Digital Convergence Initiative (DCI) specification.
-This API enables authorized external systems to securely search and synchronize with OpenSPP's registry data, promoting interoperability with other digital public infrastructure components like a Civil Registration and Vital Statistics (:term:`CRVS`) system.
+This API enables authorized external systems to securely search and synchronize with OpenSPP's registry data, promoting interoperability with other digital public infrastructure components like a Civil Registration and Vital Statistics ({term}`CRVS`) system.
 
 ## Prerequisites
 

docs/developer_guide/integrations/dci.md

@@ -9,15 +9,15 @@ myst:
 # Digital Convergence Initiative
 
 In the rapidly evolving landscape of digital public infrastructure (DPI), the principle of interoperability stands as an important foundation for building efficient, inclusive, and sustainable systems in a country.
-This article delves into how OpenSPP implemented APIs outlined in the [DCI Interface Standards v1.0](https://standards.spdci.org/standards/standards-for-interoperability-interfaces/structure-and-versioning-of-the-standards) under Registry to enable interoperability with other systems such as :term:`CRVS`.
+This article delves into how OpenSPP implemented APIs outlined in the [DCI Interface Standards v1.0](https://standards.spdci.org/standards/standards-for-interoperability-interfaces/structure-and-versioning-of-the-standards) under Registry to enable interoperability with other systems such as {term}`CRVS`.
 
 The implementation can be categorized into two sections where OpenSPP operates as the client and OpenSPP operates as the server.
 Note that currently OpenSPP has only completed the sync implementation.
 
 ## Server implementation
 
-This section focuses on utilizing OpenSPP as the source of truth for :term:`beneficiary` information where OpenSPP acts as the server.
-Such integration allows OpenSPP to seamlessly interact with other critical systems by providing data, thereby enhancing data exchange and operational :term:`efficiency`.
+This section focuses on utilizing OpenSPP as the source of truth for {term}`beneficiary` information where OpenSPP acts as the server.
+Such integration allows OpenSPP to seamlessly interact with other critical systems by providing data, thereby enhancing data exchange and operational {term}`efficiency`.
 The following steps elaborate how the module can be configured.
 
 ### Deployment and installation
@@ -64,7 +64,7 @@ The following steps elaborate how the module can be configured.
 
 This section focuses on utilizing another registry as the source for truth to get beneficiary information that can then be utilized in OpenSPP.
 
-This section focuses on utilizing another registry as the source for truth to get :term:`beneficiary` information.
+This section focuses on utilizing another registry as the source for truth to get {term}`beneficiary` information.
 The following steps elaborate how the module can be configured to fetch data where OpenSPP acts as the client.
 
 ### 2.1 Deployment and Installation

docs/developer_guide/integrations/index.md

@@ -18,7 +18,7 @@ Here, you will find detailed instructions and best practices for:
 
 - {doc}`esignet`: Discover how to integrate eSignet as an identity provider, allowing users to authenticate into OpenSPP using their MOSIP-based digital identity.
 
-- {doc}`oidc`: Follow our guide to configure Keycloak as an :term:`OIDC` provider for OpenSPP, enabling single sign-on (SSO) for a secure and streamlined user authentication experience.
+- {doc}`oidc`: Follow our guide to configure Keycloak as an {term}`OIDC` provider for OpenSPP, enabling single sign-on (SSO) for a secure and streamlined user authentication experience.
 
 ```{toctree}
 :maxdepth: 2

docs/developer_guide/integrations/oidc.md

@@ -61,7 +61,7 @@ To align with corporate branding, you can customize the login page by adding a c
 
 ### Existing users
 
-For users that already existed before the :term:`OIDC`-integration was configured, there is a need for them to go through the reset password process.
+For users that already existed before the {term}`OIDC`-integration was configured, there is a need for them to go through the reset password process.
 This is because the password is not stored in Odoo, but in Keycloak.
 Depending on the configuration, the user may have to perform 2FA setup.
 

docs/developer_guide/module_development/entitlements.md

@@ -9,7 +9,7 @@ myst:
 # Program entitlements
 
 In OpenSPP, program benefits are defined and calculated through a flexible system called **Entitlement Managers**.
-An Entitlement Manager is a self-contained component that defines the logic for how much a :term:`beneficiary` is entitled to receive in a given program cycle.
+An Entitlement Manager is a self-contained component that defines the logic for how much a {term}`beneficiary` is entitled to receive in a given program cycle.
 This allows for creating reusable and complex benefit calculation rules that can be easily attached to any program.
 
 This guide will walk you through creating a custom Entitlement Manager module from scratch.

docs/reference/modules/index.md

@@ -1,10 +1,5 @@
 
-# OpenSPP modules index
-
-```{warning}
-
-**Work in Progress**: This document is actively being developed and updated. Content may be incomplete or subject to change.
-```
+# OpenSPP modules
 
 ## SPP modules