fix: standardize capitalization in documentation headers and section titles

Author: Le-Caignec

src/use-iapp/how-to-pay/how-to-pay-for-web3telegram.md

@@ -5,7 +5,7 @@ description:
   methods for secure Telegram communication.
 ---
 
-# How to pay for Web3telegram
+# How to Pay for Web3Telegram
 
 [Web3Telegram](../web3telegram) dev tool offers secure, blockchain-based
 communication by encrypting emails and protecting user privacy.
@@ -55,7 +55,7 @@ remaining balance is automatically deducted from your account.
 For additional information on using xRLC for fallback payment in Web3Telegram,
 refer to the **Using xRLC with Web3Telegram** section.
 
-### Step 4: Execute Web3Telegram's sendTelegram Function
+### Step 4: Execute Web3Telegram's `sendTelegram` Function
 
 When using a voucher for payment, set the `useVoucher` parameter to `true`:
 
@@ -79,7 +79,7 @@ const sendTelegram = await web3telegram.sendTelegram({
 });
 ```
 
-## Using xRlC for Web3Telegram
+## Using xRLC for Web3Telegram
 
 If you choose to use xRLC to cover the computational cost of Web3Telegram (or if
 you need to cover data access costs such as retrieving the recipient's Chat Id),
@@ -138,7 +138,7 @@ Use the command below to check your balance:
 iexec.account.show();
 ```
 
-### Execute sendTelegram
+### Execute `sendTelegram`
 
 Set the `useVoucher` parameter to `false` when using Web3Telegram's sendTelegram
 function to pay with xRLC:

src/use-iapp/web3mail/advanced-configuration.md

@@ -5,7 +5,7 @@ description:
   communication.
 ---
 
-# Advanced configuration
+# Advanced Configuration
 
 The `IExecWeb3mail` constructor accepts configuration options object. As these
 options are very specific, you won't need to use them for a standard usage of

src/use-iapp/web3mail/getting-started.md

@@ -49,7 +49,7 @@ If you use it with **Webpack**, some polyfills will be needed. You can find a
 working project
 [here](https://github.com/iExecBlockchainComputing/web3mail-sdk/tree/main/demo/browser-webpack).
 
-### Instantiate with a Web3 provider
+### Instantiate with a Web3 Provider
 
 ::: code-group
 
@@ -78,7 +78,7 @@ const web3mail = new IExecWeb3mail(web3Provider);
 
 :::
 
-### Instantiate without a Web3 provider
+### Instantiate Without a Web3 Provider
 
 For projects that only require read functions, you can instantiate the SDK
 without a Web3 provider.

src/use-iapp/web3mail/methods/fetchMyContacts.md

@@ -53,7 +53,7 @@ const contactsList = await web3mail.fetchMyContacts({
 });
 ```
 
-## Return value
+## Return Value
 
 The result object contains a list of `contact` objects. Each `contact`
 represents one user who previously granted you authorization to send them

src/use-iapp/web3mail/methods/fetchUserContacts.md

@@ -73,7 +73,7 @@ const contactsList = await web3mail.fetchUserContacts({
 });
 ```
 
-## Return value
+## Return Value
 
 The result object contains a list of `contact` objects. Each `contact`
 represents one user who previously granted authorization for the user identified

src/use-iapp/web3mail/methods/sendEmail.md

@@ -308,7 +308,7 @@ const sendEmail = await web3mail.sendEmail({
 });
 ```
 
-## Return value
+## Return Value
 
 ```ts twoslash
 import { type SendEmailResponse } from '@iexec/web3mail';
@@ -322,9 +322,9 @@ This uniquely identifies the email task on the iExec side chain. You can view
 the status of the `sendEmail` method by monitoring the task on the
 [iExec Explorer](https://explorer.iex.ec/bellecour).
 
-## Error handling
+## Error Handling
 
-### Validation errors
+### Validation Errors
 
 We use [yup](https://github.com/jquense/yup) to validate input parameters.
 
@@ -352,7 +352,7 @@ try {
 }
 ```
 
-### Email schema error
+### Email Schema Error
 
 To be able to send an email to a protected data, it needs to contain, well, an
 email address.
@@ -366,7 +366,7 @@ If not, you'll get a `WorkflowError` in the form of:
 }
 ```
 
-### iExec protocol errors
+### iExec Protocol Errors
 
 In case the iExec stack is to blame, we'll make it clear and you'll get a
 specific `WorkflowError`:
@@ -379,7 +379,7 @@ specific `WorkflowError`:
 }
 ```
 
-### Workflow errors
+### Workflow Errors
 
 For any other errors, you'll get a `WorkflowError` error in the form of:
 

src/use-iapp/web3telegram/advanced-configuration.md

@@ -5,7 +5,7 @@ description:
   for secure Telegram communication on the iExec blockchain.
 ---
 
-# Advanced configuration
+# Advanced Configuration
 
 The `IExecWeb3Telegram` constructor accepts configuration options object. As
 these options are very specific, you won't need to use them for a standard usage

src/use-iapp/web3telegram/integration-guide.md

@@ -21,7 +21,7 @@ The integration process consists of the following steps:
    messages.**
 4. **Send messages securely using the Web3Telegram SDK.**
 
-## 1. Get your users to retrieve their chat ID
+## 1. Get your Users to Retrieve their Chat ID
 
 To enable messaging via Web3Telegram, you need to retrieve the recipient's Chat
 ID.
@@ -48,7 +48,7 @@ senders** can contact you.
 
 :::
 
-## 2. Create the protected data with data protector SDK
+## 2. Create the Protected Data with Data Protector SDK
 
 After obtaining your user's Chat ID, you need to protect it using iExec’s Data
 Protector to ensure privacy and security.
@@ -64,7 +64,7 @@ const protectedData = await dataProtectorCore.protectData({
 });
 ```
 
-## 3. Grant access via data protector SDK
+## 3. Grant Access via Data Protector SDK
 
 To allow users to send messages, you must explicitly grant access to specific
 users.
@@ -85,7 +85,7 @@ const grantedAccess = await dataProtectorCore.grantAccess({
 });
 ```
 
-## 4. Send messages via Web3Telegram SDK
+## 4. Send Messages via Web3Telegram SDK
 
 Once authorized, a user can send messages via Web3Telegram SDK.
 

src/use-iapp/web3telegram/methods/fetchMyContacts.md

@@ -53,7 +53,7 @@ const contactsList = await web3telegram.fetchMyContacts({
 });
 ```
 
-## Return value
+## Return Value
 
 The result object contains a list of `contact` objects. Each `contact`
 represents one user who previously granted you authorization to send them

src/use-iapp/web3telegram/methods/fetchUserContacts.md

@@ -73,7 +73,7 @@ const contactsList = await web3telegram.fetchUserContacts({
 });
 ```
 
-## Return value
+## Return Value
 
 The result object contains a list of `contact` objects. Each `contact`
 represents one user who previously granted authorization for the user identified