Consistent capitalization

content/en/docs/Configuration/ampint-environment-properties.md

@@ -28,7 +28,7 @@ The following environment properties must be set up in each customer's data plan
 | Environment Property Name                                                | Description  |
 |--------------------------------------------------------------------------|--------------|
 | Connections_APIFrontendUrl                                               | URL to access the FDX APIs <br />**Example**:`https://griffin-design.openbanking.example.net:4443/`   |
-| Connections_realmName                                                    | Realm Name in the authorization server representing customer tenant <br />**Example**: griffin-design |
+| Connections_realmName                                                    | Realm Name in the Authorization Server representing customer tenant <br />**Example**: griffin-design |
 | FDX_Accounts_Search_basePath                                             | Basepath of the FDX Accounts API <br />**Default**: /fdx/v6/core/accounts                             |
 | FDX_Authorization_consentDurationOneTimePeriod                           | Default duration value (in days) for ONE_TIME consent <br />**Default**: 1                            |
 | FDX_Authorization_consentDurationPersistentPeriod                        | Default long time duration of PERSISTENT consent <br />**Default**: 36525                             |
@@ -39,12 +39,12 @@ The following environment properties must be set up in each customer's data plan
 | FDX_Authorization_consentLookbackPeriodMin                               | Minimum allowed lookback period (in days) for which historical data may be requested; measured from request time, not grant time <br />**Default**: 1  |
 | FDX_Authorization_consentSupportedDataClusters                           | Supported enumerations or types of the clusters of data elements that can be requested in a consent grant <br />**Default**: ACCOUNT_BASIC,ACCOUNT_DETAILED,TRANSACTIONS,STATEMENTS,CUSTOMER_CONTACT,CUSTOMER_PERSONAL,INVESTMENTS,PAYMENT_SUPPORT |
 | FDX_Authorization_consentSupportedResourceTypes                          | Types of resources that can be requested and for which consent can be given <br />**Default**: ACCOUNT |
-| FDX_Authorization_wellKnownNotSupportedKeys                              | The keys of a well known URI's response coming from the authorization server that need to be suppressed before sending the response <br />**Default**: introspection_endpoint,userinfo_endpoint,end_session_endpoint,check_session_iframe,device_authorization_endpoint,backchannel_authentication_endpoint,registration_endpoint |
+| FDX_Authorization_wellKnownNotSupportedKeys                              | The keys of a well known URI's response coming from the Authorization Server that need to be suppressed before sending the response <br />**Default**: introspection_endpoint,userinfo_endpoint,end_session_endpoint,check_session_iframe,device_authorization_endpoint,backchannel_authentication_endpoint,registration_endpoint |
 | FDX_Kafka_Publish_Notification_priority                                  | Priority level of the logged events <br />**Default**: MEDIUM                                        |
 | FDX_Kafka_Publish_Notification_severity                                  | Severity level of the logged events <br />**Default**: INFO                                          |
 | FDX_Kafka_Publish_Notification_tenantType                                | Type of the tenant <br />**Default**: DATA_PROVIDER                                                  |
 | FDX_Notification_Subscription_eventTypes                                 | Supported event types for subscription <br />**Default**: CONSENT_PARTIALLY_AUTHORIZED,CONSENT_AUTHORIZED,CONSENT_REJECTED,CONSENT_ON_HOLD,CONSENT_CONSUMED,CONSENT_EXPIRED,CONSENT_MODIFIED |
-| Generic_Authorization_loginUrl                                           | Login url of the authorization server <br />**Example**: `https://auth.openbanking.example.net/realms/griffin-design/protocol/openid-connect/auth`|
+| Generic_Authorization_loginUrl                                           | Login url of the Authorization Server <br />**Example**: `https://auth.openbanking.example.net/realms/griffin-design/protocol/openid-connect/auth`|
 | Generic_Authorization_maxConsentAllowedPerUserPerPartner                 | Maximum number of allowed consents per user per partner <br />**Default**: 10                         |
 | Generic_Authorization_scaMethodEnabled                                   | If strong customer authentication is enabled <br />**Default**: TRUE                                  |
 | Generic_Authorization_scaMethodExplanation                               | Description of the SCA method used                                                                |

content/en/docs/Release-Notes/401_openbanking_relnotes.md

@@ -6,11 +6,11 @@ date: 2025-02-06
 ---
 This update contains several new features and improvements.
 
-## Consent management updates
+## Consent Management updates
 
 * A new feature has been added to capture the timestamp of consent acknowledgement. This enhancement improves tracking and auditing capabilities for user consent processes.
 
-* A new authorization timestamp has been added to the consent admin dashboard. This feature provides administrators with more detailed information about consent authorizations.
+* A new authorization timestamp has been added to the Consent Admin Dashboard. This feature provides administrators with more detailed information about consent authorizations.
 
 ## Performance updates
 

content/en/docs/Release-Notes/402_openbanking_relnotes.md

@@ -15,10 +15,10 @@ This update contains several new features, enhancements, and performance improve
 * Added support to store the **`termsAndConditionVersion`** in the consent metadata via consent grant app.  
   This ensures accurate version tracking of the terms and conditions accepted during the consent process.
 
-* **Authorization timestamp** has been added to the consent admin dashboard.  
+* **Authorization timestamp** has been added to the Consent Admin Dashboard.  
   This provides administrators with improved visibility into the timing of consent authorizations.
 
-* Timestamps have been **re-arranged in the consent admin dashboard** to improve the user interface and readability.
+* Timestamps have been **re-arranged in the Consent Admin Dashboard** to improve the user interface and readability.
 
 ## Performance updates
 

content/en/docs/Release-Notes/403_openbanking_relnotes.md

@@ -7,9 +7,9 @@ date: 2025-07-31
 
 This update contains several new features and enhancements.
 
-## Consent management update
+## Consent Management update
 
-* The consent admin dashboard now displays the **terms and conditions version** information.  
+* The Consent Admin Dashboard now displays the **terms and conditions version** information.  
   This provides administrators with improved visibility into the terms and conditions version the customer authorized.
 
 ## API update
@@ -19,5 +19,5 @@ This update contains several new features and enhancements.
 
 ## Authorization Server update
 
-* The authorization server now supports **external custom login page redirection**.  
-  This allows you to set up the authorization server to redirect customers to data provider's custom login page. This feature is particularly useful when there is no OIDC/SAML compatible Identity Provider available to connect with.
+* The Authorization Server now supports **external custom login page redirection**.  
+  This allows you to set up the Authorization Server to redirect customers to data provider's custom login page. This feature is particularly useful when there is no OIDC/SAML compatible Identity Provider available to connect with.

content/en/docs/Release-Notes/410_openbanking_relnotes.md

@@ -7,10 +7,10 @@ date: 2025-11-28
 
 This update contains several new features and enhancements.
 
-## Consent management update
+## Consent Management update
 
 * A new endpoint is added in Consent Management API (Participant Resource Admin API) to revoke all consents for a given user.
-* Consent management now allows you to add account nickname in consent data. This functionality is provided by External Resource Authentication API.
+* Consent Management now allows you to add account nickname in consent data. This functionality is provided by External Resource Authentication API.
 * Resource owner information is now available in Consent Admin Dashboard, consent details page.
 
 ## Authorization Server update

content/en/docs/Validation/fdx/_index.md

@@ -47,7 +47,7 @@ Configure Postman for testing Open Banking APIs.
 
 3. Click **Certificates**. Ensure a TPP client certificate is installed for the target environment. If not:
     * Click **Add Certificate**.
-    * Type the target host for the Authorization server (auth-server environment variable) and leave the port empty (if exposed on 443 as by default).
+    * Type the target host for the Authorization Server (auth-server environment variable) and leave the port empty (if exposed on 443 as by default).
     * Select the certificate and private key (CRT file and KEY file respectively) to be used for MTLS connection.
     * Click **Add**.
     * Click **Add Certificate**.
@@ -84,9 +84,9 @@ Use Postman to test the FDX Core API. Before sending any request make sure that
 
 Continue testing the Core API in the Browser.
 
-* Open the link to the login page in your browser and login with an authorized user. The login page depends on the Authorization server configuration.
+* Open the link to the login page in your browser and login with an authorized user. The login page depends on the Authorization Server configuration.
 
-* Select the bank accounts that correspond to the user consent, and confirm. The consent page depends on the Authorization server configuration.
+* Select the bank accounts that correspond to the user consent, and confirm. The consent page depends on the Authorization Server configuration.
 The redirect URL of the DR client app should include `https://oauth.pstmn.io/v1/callback` and the link back to Postman with the authorization code to use for the next step.
 
 * Copy the value of query parameter `code` from the redirected URL.

content/en/docs/api_security_guide/api-security.md

@@ -82,7 +82,7 @@ The following APIs are for Data Recipients and Data Aggregators to consume and b
 
 ### Solution APIs
 
-The following APIs are for Data Providers to integrate with our consent management module.
+The following APIs are for Data Providers to integrate with our Consent Management module.
 
 #### External Resource Authentication API
 

src/plant-uml/obb-end-to-end-web-journey.puml

@@ -180,7 +180,7 @@ API_GATEWAY <-- IAM: Response
 API_GATEWAY -> API_GATEWAY: Verify Access Token scope
 
 note right of API_GATEWAY
-The consent management API provides separate operations based on the type of consent i.e.
+The Consent Management API provides separate operations based on the type of consent i.e.
 account information, payments, etc. The API Gateway mediates the request and
 calls the operation appropriate to the consent in question.
 end note