diff --git a/README.md b/README.md
index 6f23ceb9c..f2c07f7a8 100644
--- a/README.md
+++ b/README.md
@@ -57,6 +57,30 @@ Here is a reference to "talkable section": :ref:`talkable-section` which will ha
 name "Talkable Section".
 ```
 
+### General Formatting Rules for Documentation
+
+**Directives (`..` syntax)**:
+
+* All directives starting with `..` (e.g., `.. image::`, `.. note::`) must have **2 spaces** indentation for their content. Examples:
+
+    ```rst
+    .. meta::
+      :description: This is an example of a meta directive.
+
+    .. image:: /_static/img/example.jpg
+      :alt: Example Image
+
+    .. note::
+      This is an important note.
+    
+    .. code-block:: html
+      <h1>Hello world!</h1>
+    ```
+
+#### Empty Line at the End of Files
+
+Always ensure there is a blank line at the end of each file to adhere to formatting standards.
+
 Build the documentation
 -----------------------
 
diff --git a/source/advanced_features.rst b/source/advanced_features.rst
index a2e962f9c..562cfe443 100644
--- a/source/advanced_features.rst
+++ b/source/advanced_features.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable provides optional features for your referral program. Unlock them to increase conversions.
+  :description: Talkable provides optional features for your referral program. Unlock them to increase conversions.
 
 Features
 ########
@@ -12,85 +12,85 @@ and make your referral program incredibly easy to manage. Here’s an overview o
 each with links to integration details.
 
 .. list-table::
-   :widths: 35 65
+  :widths: 35 65
 
-   * - :ref:`Automatic Coupon Creation <advanced_features/coupons>`
-     - Issue single and multi-use coupons for your campaigns
+  * - :ref:`Automatic Coupon Creation <advanced_features/coupons>`
+    - Issue single and multi-use coupons for your campaigns
 
-   * - :ref:`Shopify Coupon auto-sync <advanced_features/shopify_coupons_auto_sync>`
-     - Issue coupons automatically for your Shopify store
+  * - :ref:`Shopify Coupon auto-sync <advanced_features/shopify_coupons_auto_sync>`
+    - Issue coupons automatically for your Shopify store
 
-   * - :ref:`Shopify Coupon auto-apply <advanced_features/shopify_coupons_auto_apply>`
-     - Issue coupons automatically for your Shopify store
+  * - :ref:`Shopify Coupon auto-apply <advanced_features/shopify_coupons_auto_apply>`
+    - Issue coupons automatically for your Shopify store
 
-   * - :ref:`Shopify Purchase Syncing <advanced_features/shopify_purchase_syncing>`
-     - Automatic purchases synchronization from your Shopify store
+  * - :ref:`Shopify Purchase Syncing <advanced_features/shopify_purchase_syncing>`
+    - Automatic purchases synchronization from your Shopify store
 
-   * - :ref:`Referral Tracking Methods <advanced_features/track_methods>`
-     - See how Talkable tracks referrals and what data is used in the tracking process
+  * - :ref:`Referral Tracking Methods <advanced_features/track_methods>`
+    - See how Talkable tracks referrals and what data is used in the tracking process
 
-   * - :ref:`Advocate Personal Coupon Sharing <advanced_features/personal_coupon_sharing>`
-     - Find out how to add personal coupon sharing into a Talkable campaign in addition to link sharing
+  * - :ref:`Advocate Personal Coupon Sharing <advanced_features/personal_coupon_sharing>`
+    - Find out how to add personal coupon sharing into a Talkable campaign in addition to link sharing
 
-   * - :ref:`Convert static copy into Localization <advanced_features/converting_into_localization>`
-     - Convert all static languange into a customizable copy that’s
-       easy to AB test.
+  * - :ref:`Convert static copy into Localization <advanced_features/converting_into_localization>`
+    - Convert all static languange into a customizable copy that’s
+      easy to AB test.
 
-   * - :ref:`Сustomer Service Portal <advanced_features/customer_service_portal>`
-     - Explore full details for each individual customer and their referral journey,
-       manage their rewards and deliver excellent customer service.
+  * - :ref:`Сustomer Service Portal <advanced_features/customer_service_portal>`
+    - Explore full details for each individual customer and their referral journey,
+      manage their rewards and deliver excellent customer service.
 
-   * - :ref:`Params encryption <advanced_features/params_encryption>`
-     - For additional security, it is possible to encrypt Advocate, Friend and Loyalty member emails on back-end,
-       as well as their custom properties.
+  * - :ref:`Params encryption <advanced_features/params_encryption>`
+    - For additional security, it is possible to encrypt Advocate, Friend and Loyalty member emails on back-end,
+      as well as their custom properties.
 
-   * - :ref:`File encryption <advanced_features/file_encryption>`
-     - For additional security, it is possible to encrypt files.
+  * - :ref:`File encryption <advanced_features/file_encryption>`
+    - For additional security, it is possible to encrypt files.
 
-   * - :ref:`Report password protection <advanced_features/report_password_protection>`
-     - For additional security, reports have password protection by default.
+  * - :ref:`Report password protection <advanced_features/report_password_protection>`
+    - For additional security, reports have password protection by default.
 
-   * - :ref:`Including Product Items <advanced_features/product_items>`
-     - Let your customers share specific items that they’ve purchased
-       and pass product details along with purchase data
+  * - :ref:`Including Product Items <advanced_features/product_items>`
+    - Let your customers share specific items that they’ve purchased
+      and pass product details along with purchase data
 
-   * - :ref:`Integrating Events <advanced_features/events>`
-     - Fits SaaS, subscription-based, and other businesses that require integrating
-       additional events to build more advanced referral logics on top of regular
-       purchases.
+  * - :ref:`Integrating Events <advanced_features/events>`
+    - Fits SaaS, subscription-based, and other businesses that require integrating
+      additional events to build more advanced referral logics on top of regular
+      purchases.
 
-   * - :ref:`Pass custom user data <advanced_features/passing_custom_data>`
-     - Pass additional data to Talkable to operate with it inside campaigns
+  * - :ref:`Pass custom user data <advanced_features/passing_custom_data>`
+    - Pass additional data to Talkable to operate with it inside campaigns
 
-   * - :ref:`Phone number gating <advanced_features/phone_number_gating>`
-     - Collect customers' phone numbers and sync with ESPs.
+  * - :ref:`Phone number gating <advanced_features/phone_number_gating>`
+    - Collect customers' phone numbers and sync with ESPs.
 
-   * - :ref:`Referrals Approval <advanced_features/referrals_approval>`
-     - Learn about Talkable Fraud settings, why they are important
-       and how to find a right Fraud Profile that works best for your site.
+  * - :ref:`Referrals Approval <advanced_features/referrals_approval>`
+    - Learn about Talkable Fraud settings, why they are important
+      and how to find a right Fraud Profile that works best for your site.
 
-   * - :ref:`Segments <advanced_features/segments>`
-     - Brings more power and flexibility into segmenting your reporting
+  * - :ref:`Segments <advanced_features/segments>`
+    - Brings more power and flexibility into segmenting your reporting
 
-   * - :ref:`Subscribing to Talkable Iframe events <advanced_features/subscribing_to_events>`
-     - Subscribe to Talkable Iframe events such as the campaign is loaded or closed and
-       perform some updates to your site based on them.
+  * - :ref:`Subscribing to Talkable Iframe events <advanced_features/subscribing_to_events>`
+    - Subscribe to Talkable Iframe events such as the campaign is loaded or closed and
+      perform some updates to your site based on them.
 
-   * - :ref:`Setting up Campaign Placement criteria <advanced_features/reg_ex>`
-     - Walking through a Campaign Placement criteria setup that can support multiple
-       matching techniques
+  * - :ref:`Setting up Campaign Placement criteria <advanced_features/reg_ex>`
+    - Walking through a Campaign Placement criteria setup that can support multiple
+      matching techniques
 
-   * - :ref:`Using URL Parameters <advanced_features/url_parameters>`
-     - Override some of the parameters right through URL query string
+  * - :ref:`Using URL Parameters <advanced_features/url_parameters>`
+    - Override some of the parameters right through URL query string
 
-   * - :ref:`UTM Tags <advanced_features/utm_tags>`
-     - Brings more power and flexibility into segmenting your reporting by UTM tags
+  * - :ref:`UTM Tags <advanced_features/utm_tags>`
+    - Brings more power and flexibility into segmenting your reporting by UTM tags
 
-   * - :ref:`White Labeling <advanced_features/white_labeling>`
-     - Change all visible URLs to your domain instead of talkable.com
+  * - :ref:`White Labeling <advanced_features/white_labeling>`
+    - Change all visible URLs to your domain instead of talkable.com
 
-   * - :ref:`Multi-Currency <advanced_features/multi_currency>`
-     - Accept multiple currencies and set different rewards per currency
+  * - :ref:`Multi-Currency <advanced_features/multi_currency>`
+    - Accept multiple currencies and set different rewards per currency
 
 .. container:: hidden
 
diff --git a/source/advanced_features/converting_into_localization.rst b/source/advanced_features/converting_into_localization.rst
index 25e586161..d963fafed 100644
--- a/source/advanced_features/converting_into_localization.rst
+++ b/source/advanced_features/converting_into_localization.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This is a how-to guide to help you get the most out of Localizations.
+  :description: This is a how-to guide to help you get the most out of Localizations.
 
 Converting Into Localization
 ============================
@@ -57,7 +57,7 @@ A piece that we are going to extract into Localizations is just a copy, without
 
 .. warning::
 
-   Talkable does not allow coding up Localizations within CSS area. If you want to move some CSS property into localizations use inline <style> tag inside HTML area.
+  Talkable does not allow coding up Localizations within CSS area. If you want to move some CSS property into localizations use inline <style> tag inside HTML area.
 
 Moving Subject Line Into Localization
 -------------------------------------
@@ -194,4 +194,4 @@ In order to chieve this AB test we need to
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/coupons.rst b/source/advanced_features/coupons.rst
index f16c3f50f..ac6d1aba4 100644
--- a/source/advanced_features/coupons.rst
+++ b/source/advanced_features/coupons.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can reward Advocate and their Friend with coupons. Talkable supports both one-time-use coupons as well as multi-use coupons.
+  :description: You can reward Advocate and their Friend with coupons. Talkable supports both one-time-use coupons as well as multi-use coupons.
 
 Coupons
 =======
@@ -35,7 +35,7 @@ There are several steps that need to be taken for this scenario:
 
 .. raw:: html
 
-   <h2>REST API to Create Coupons</h2>
+  <h2>REST API to Create Coupons</h2>
 
 Talkable can create coupons via a webhook using your REST API endpoint.
 Read :ref:`Create Coupon Webhook Documentation <web_hooks/create_coupon>` for implementation details.
@@ -47,7 +47,7 @@ Read :ref:`Shopify coupon auto-sync documentation <advanced_features/shopify_cou
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
 
 Requirements
 ------------
@@ -59,18 +59,18 @@ Only the following characters are allowed in a coupon code:
 
 .. code-block:: text
 
-   A-Z 0-9 - _ / . % : * + @ & #
+  A-Z 0-9 - _ / . % : * + @ & #
 
 .. note::
-   Spaces are forbidden.
+  Spaces are forbidden.
 
 Try to avoid ambiguous characters. This simple solution generates a string of easily readable characters for activation codes.
 We do not want people confusing 8 with B, 1 with I, 0 with O, L with 1, etc.
 
 .. code-block:: ruby
 
-   # Generates a random string from a set of easily readable characters
-   def generate_activation_code(size = 6)
-     charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
-     (0...size).map { charset[rand(charset.size)] }.join
-   end
+  # Generates a random string from a set of easily readable characters
+  def generate_activation_code(size = 6)
+    charset = ["2", "3", "4", "6", "7", "9", "A", "C", "D", "E", "F", "G", "H", "J", "K", "M", "N", "P", "Q", "R", "T", "V", "W", "X", "Y", "Z"]
+    (0...size).map { charset[rand(charset.size)] }.join
+  end
diff --git a/source/advanced_features/customer_service_portal.rst b/source/advanced_features/customer_service_portal.rst
index 63257be03..ba5106b51 100644
--- a/source/advanced_features/customer_service_portal.rst
+++ b/source/advanced_features/customer_service_portal.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Customer Service Portal
+  :description: Customer Service Portal
 
 Customer Service Portal
 =======================
@@ -13,13 +13,13 @@ excellent customer service.
 Contents:
 
 .. toctree::
-   :maxdepth: 2
+  :maxdepth: 2
 
-   customer_service_portal/overview
-   customer_service_portal/terminology
-   customer_service_portal/use_case_1
-   customer_service_portal/use_case_2
-   customer_service_portal/use_case_3
-   customer_service_portal/use_case_4
-   customer_service_portal/use_case_5
-   customer_service_portal/use_case_6
\ No newline at end of file
+  customer_service_portal/overview
+  customer_service_portal/terminology
+  customer_service_portal/use_case_1
+  customer_service_portal/use_case_2
+  customer_service_portal/use_case_3
+  customer_service_portal/use_case_4
+  customer_service_portal/use_case_5
+  customer_service_portal/use_case_6
diff --git a/source/advanced_features/customer_service_portal/overview.rst b/source/advanced_features/customer_service_portal/overview.rst
index be446365d..4930087f6 100644
--- a/source/advanced_features/customer_service_portal/overview.rst
+++ b/source/advanced_features/customer_service_portal/overview.rst
@@ -21,10 +21,10 @@ The Customer Service Portal provides a simple search box that will allow you to
   If no county code is given, Talkable will try applying the USA and Canada codes and search with the resulting number.
 - **Order number**: the order number of a purchase.
 - **Coupon code**: the single-use coupon code issued as a reward to a referral program user.
-- **Personal coupon code**: the :ref:`personal coupon code <advanced_features/personal_coupon_sharing>`, shared by an Advocate
+- **Personal coupon code**: the :ref:`personal coupon code <advanced_features/personal_coupon_sharing>`, shared by an Advocate.
 
 The search query might produce multiple results. In such case, every matched user will be listed,
-showing some personal info (email and phone number) and, if present, other matched fields (i.e. order number and/or coupon code).
+showing some personal info (email and phone number) and, if present, other matched fields (i.e., order number and/or coupon code).
 To see more personal details, select a user from the list.
 
 Example of Customer Service Portal person lookup:
@@ -33,4 +33,4 @@ Example of Customer Service Portal person lookup:
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/terminology.rst b/source/advanced_features/customer_service_portal/terminology.rst
index db831d078..5a92d642a 100644
--- a/source/advanced_features/customer_service_portal/terminology.rst
+++ b/source/advanced_features/customer_service_portal/terminology.rst
@@ -12,35 +12,36 @@ Advocate’s invite (a share). A referral will not be created unless the followi
 Friend Email, and a Purchase made by a Referred Friend. Each referral is passed through several fraud checks
 (configured inside Fraud Settings). As a result of the fraud checks each referral status can be:
 
- 1. **In progress**: Talkable referral engine is processing the referral. Such action usually takes less than a second
-    so it is highly unlikely that you will see this status. No rewards are issued at this point.
-
- 2. **Pending**: a referral is pending approval. Talkable referral engine approves pending referrals automatically
-    with a delay set under fraud settings. A user can also approve a referral manually until the auto-approval happens.
-    Thus, if the referral fraud checks were passed successfully each referral will eventually become approved.
-    No rewards are issued up until approval.
-
- 3. **Flagged**: due to having many different options to configure referral fraud checks,
-    it is not always possible to set up an automatic resolution for each referral.
-    For such cases, you may want to Flag referrals that are in a so-called grey area,
-    where the chance of fraud is around 50% and it is impossible to make the decision automatically.
-    All flagged referrals are added to a queue and can be accessed inside CSP → Referrals.
-    No rewards are issued at this point. All flagged referrals will be automatically resolved
-    to either voided or approved status, depending on the fraud settings configuration.
-    It is recommended to void flagged referrals automatically so you can only approve valid ones manually.
-    As a result this can save lots of time as most flagged referrals are rather suspicious than valid.
-
- 4. **Approved**: this is a valid referral status which either gets set by the Talkable referral engine
-    or by a user. Flagged referrals can also turn to approved. All rewards associated
-    with the referral are then passed to the next stage to verify if they
-    can be issued.
-
- 5. **Voided**: this status is set by a user manually if they decide a referral is invalid and there should be no
-    rewards issued as a result. Only pending and flagged referrals can be voided. Talkable referral engine cannot set
-    this status automatically. All rewards associated with the referral are getting blocked as a result.
-
- 6. **Blocked**: when some fraud checks are failed Talkable referral engine blocks the referral immediately. All rewards
-    associated with the referral are getting blocked as a result.
+1. **In progress**: Talkable referral engine is processing the referral. Such action usually takes less than a second
+   so it is highly unlikely that you will see this status. No rewards are issued at this point.
+
+2. **Pending**: a referral is pending approval. Talkable referral engine approves pending referrals
+   automatically with a delay set under fraud settings. A user can also approve a referral manually until
+   the auto-approval happens. Thus, if the referral fraud checks were passed successfully, each referral
+   will eventually become approved. No rewards are issued up until approval.
+
+3. **Flagged**: due to having many different options to configure referral fraud checks,
+   it is not always possible to set up an automatic resolution for each referral. For such
+   cases, you may want to Flag referrals that are in a so-called grey area, where the
+   chance of fraud is around 50% and it is impossible to make the decision automatically.
+   All flagged referrals are added to a queue and can be accessed inside CSP → Referrals.
+   No rewards are issued at this point. All flagged referrals will be automatically resolved
+   to either voided or approved status, depending on the fraud settings configuration.
+   It is recommended to void flagged referrals automatically so you can only approve valid
+   ones manually. As a result, this can save lots of time as most flagged referrals are
+   rather suspicious than valid.
+
+4. **Approved**: this is a valid referral status which either gets set by the Talkable referral engine
+   or by a user. Flagged referrals can also turn to approved. All rewards associated with
+   the referral are then passed to the next stage to verify if they can be issued.
+
+5. **Voided**: this status is set by a user manually if they decide a referral is invalid and there
+   should be no rewards issued as a result. Only pending and flagged referrals can be voided.
+   Talkable referral engine cannot set this status automatically. All rewards associated
+   with the referral are getting blocked as a result.
+
+6. **Blocked**: when some fraud checks are failed Talkable referral engine blocks the referral immediately. All rewards
+   associated with the referral are getting blocked as a result.
 
 Reward
 ------
@@ -62,4 +63,4 @@ This is what the person gets as a result of some action (incentive). Available r
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_1.rst b/source/advanced_features/customer_service_portal/use_case_1.rst
index 6bf5173d9..d71b0c271 100644
--- a/source/advanced_features/customer_service_portal/use_case_1.rst
+++ b/source/advanced_features/customer_service_portal/use_case_1.rst
@@ -51,4 +51,4 @@ This looks like a valid referral. Let’s move on to
 
 .. container:: hidden
 
-   .. toctree::
\ No newline at end of file
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_2.rst b/source/advanced_features/customer_service_portal/use_case_2.rst
index 0cb4b70f8..a00947ebe 100644
--- a/source/advanced_features/customer_service_portal/use_case_2.rst
+++ b/source/advanced_features/customer_service_portal/use_case_2.rst
@@ -62,4 +62,4 @@ Here is what email statuses mean:
 
 .. container:: hidden
 
-   .. toctree::
\ No newline at end of file
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_3.rst b/source/advanced_features/customer_service_portal/use_case_3.rst
index 7a0fa6ae7..0301cd6df 100644
--- a/source/advanced_features/customer_service_portal/use_case_3.rst
+++ b/source/advanced_features/customer_service_portal/use_case_3.rst
@@ -97,4 +97,4 @@ We identify this in the same way as described above.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_4.rst b/source/advanced_features/customer_service_portal/use_case_4.rst
index 1924dec80..26df72a86 100644
--- a/source/advanced_features/customer_service_portal/use_case_4.rst
+++ b/source/advanced_features/customer_service_portal/use_case_4.rst
@@ -54,4 +54,4 @@ flagged/blocked ones. We see that the blocked reason in this case is “Matching
 
 .. container:: hidden
 
-   .. toctree::
\ No newline at end of file
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_5.rst b/source/advanced_features/customer_service_portal/use_case_5.rst
index a57d186e8..813d023fb 100644
--- a/source/advanced_features/customer_service_portal/use_case_5.rst
+++ b/source/advanced_features/customer_service_portal/use_case_5.rst
@@ -11,13 +11,13 @@ on social media pages.
 To blocklist a user, first navigate to the “Blocklist” section of the Customer Service Portal:
 
 .. image:: /_static/img/advanced_features/customer_service_portal/blocklist.png
-   :width: 644 px
+  :width: 644 px
 
 Adding a user to the blocklist
 ------------------------------
 
 .. image:: /_static/img/advanced_features/customer_service_portal/adding_blocklist.png
-   :width: 436 px
+  :width: 436 px
 
 (We support adding users to a blocklist using two methods, by Email or by IP address. To add an email to the
 blocklist, just enter the email into the "Blocked emails” field and press “Save Changes”. Note that emails are
@@ -47,4 +47,4 @@ all you have to do to take a user off the blocklist is to delete their email or
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/customer_service_portal/use_case_6.rst b/source/advanced_features/customer_service_portal/use_case_6.rst
index a79bc0599..02a0c434b 100644
--- a/source/advanced_features/customer_service_portal/use_case_6.rst
+++ b/source/advanced_features/customer_service_portal/use_case_6.rst
@@ -53,4 +53,4 @@ on the screenshot above.
 
 .. container:: hidden
 
-   .. toctree::
\ No newline at end of file
+  .. toctree::
diff --git a/source/advanced_features/events.rst b/source/advanced_features/events.rst
index b32f8e3ad..7499e284b 100644
--- a/source/advanced_features/events.rst
+++ b/source/advanced_features/events.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: In addition to regular referral campaigns, Talkable also supports custom events that can be split into multiple categories.
+  :description: In addition to regular referral campaigns, Talkable also supports custom events that can be split into multiple categories.
 
 Integrating Events
 ==================
@@ -47,7 +47,7 @@ can be found in the Reports → Events section of your Talkable Dashboard. Here
 
 .. note::
 
-   Please make sure you've added :ref:`Talkable Initialization Script <integration/custom/integration_components/initialization_script>` to your header or any template spanning every page.
+  Please make sure you've added :ref:`Talkable Initialization Script <integration/custom/integration_components/initialization_script>` to your header or any template spanning every page.
 
 One-time purchases should go under the “purchase” event category. You can find all purchases
 in the Reports → Purchases section of your Talkable Dashboard. Here is an example:
@@ -73,10 +73,10 @@ in the Reports → Purchases section of your Talkable Dashboard. Here is an exam
 
 .. note::
 
-   All recurring subscription purchases should be passed to Talkable as well, to ensure
-   data integrity. If recurring transactions occur on the backend, follow the
-   |br|
-   :ref:`Origin API <api_v2/origins>` (see “Create an event” section).
+  All recurring subscription purchases should be passed to Talkable as well, to ensure
+  data integrity. If recurring transactions occur on the backend, follow the
+  |br|
+  :ref:`Origin API <api_v2/origins>` (see “Create an event” section).
 
 .. _advanced_features/events/available_properties:
 
@@ -85,81 +85,81 @@ Available properties
 
 .. note::
 
-   All PII params support data encryption. Find more about :ref:`Params Encryption <advanced_features/params_encryption>`.
+  All PII params support data encryption. Find more about :ref:`Params Encryption <advanced_features/params_encryption>`.
 
 Here is a list of available properties each event can include:
 
 .. container:: ptable
 
-   ===================== =================================================================
-   Property              Description
-   ===================== =================================================================
-   **event**             An event data:
-
-                         * **event_category** (required) – a category under which the event should be
-                           tracked. Only alpha-numeric characters and underscores are
-                           allowed. Minimum length – 5 characters. |br|
-                           Example: ``'subscription'``.
-                         * **event_number** (required) – any alpha-numeric characters. Each event
-                           should have a unique event number, duplicate events will not be
-                           saved. |br|
-                           Example: ``'18934671af'``.
-                         * **subtotal** (optional) – event subtotal. Any valid positive number
-                           (including floats) or 0 are allowed. Preferably it should be passed
-                           as a string to avoid JavaScript issues with rounding floats. |br|
-                           Example: ``'198.5'``.
-                         * **coupon_code** (optional) – a coupon code that was applied to
-                           this event. |br|
-                           Example: ``'SAVE20'``. You can also pass multiple coupons as
-                           an array: ``['SAVE20', 'SAVE5']`` if they were stacked.
-                         * **currency_iso_code** (optional) - Currency ISO code is required
-                           for multi-currency sites. |br|
-                           Example: ``'USD'``.
-                         * **shipping_address** (optional) – Shipping address in case an event is
-                           shippable. It is used in fraud prevention. |br|
-                           Example:
-                           ``'475 Valencia St, 2nd Floor, San Francisco, 94103, USA'``.
-                         * **shipping_zip** (optional) – Same as **shipping_address**. Include only
-                           zip here. |br|
-                           Example: ``94103``.
-
-   **customer**          A person who issued an event:
-
-                         * **email**. (required) |br|
-                           Example: ``'customer@example.com'``.
-                         * **first_name** (optional). |br|
-                           Example: ``'John'``.
-                         * **last_name** (optional) |br|
-                           Example: ``'Smith'``.
-                         * **traffic_source** (optional) - specific
-                           :ref:`Traffic Source <advanced_features/segments>` value
-                           that helps to distinguish different points of integration. |br|
-                           Example: ``'facebook'``.
-
-   **campaign_tags**     Campaign tags are used to manually choose which campaign to show
-                         once the event has been tracked successfully (optional).
-
-                         Each Talkable campaign supports multiple tags, you can list them
-                         as an array: ``['tag1', 'tag2']``.
-
-                         You can control campaign tags inside Campaign Rules. Each
-                         Talkable campaign can have different tags.
-
-                         Alternatively, you can use
-                         :ref:`Campaign Placements <campaigns/campaign_placements>`
-                         feature to set up routing in your Talkable Dashboard instead
-                         of controlling it through the JS integration on your end. Campaign
-                         Placements are easy to change, no code changes are needed on your
-                         end.
-
-   **custom_properties** Custom key-value data that can be attached to a person
-                         (optional). It can be used for segmentation for example: you can
-                         code up custom criteria to show relevant campaigns to
-                         each segment. Alternatively, custom properties can be used for an
-                         advanced referral reward logics. Any valid JS object is allowed.
-                         Object value should always be a string.
-
-                         Example: ``{ key1: 'value1', key2: 'true' }``.
-                         :ref:`Learn more <advanced_features/passing_custom_data>`.
-
-   ===================== =================================================================
+  ===================== =================================================================
+  Property              Description
+  ===================== =================================================================
+  **event**             An event data:
+
+                        * **event_category** (required) – a category under which the event should be
+                          tracked. Only alpha-numeric characters and underscores are
+                          allowed. Minimum length – 5 characters. |br|
+                          Example: ``'subscription'``.
+                        * **event_number** (required) – any alpha-numeric characters. Each event
+                          should have a unique event number, duplicate events will not be
+                          saved. |br|
+                          Example: ``'18934671af'``.
+                        * **subtotal** (optional) – event subtotal. Any valid positive number
+                          (including floats) or 0 are allowed. Preferably it should be passed
+                          as a string to avoid JavaScript issues with rounding floats. |br|
+                          Example: ``'198.5'``.
+                        * **coupon_code** (optional) – a coupon code that was applied to
+                          this event. |br|
+                          Example: ``'SAVE20'``. You can also pass multiple coupons as
+                          an array: ``['SAVE20', 'SAVE5']`` if they were stacked.
+                        * **currency_iso_code** (optional) - Currency ISO code is required
+                          for multi-currency sites. |br|
+                          Example: ``'USD'``.
+                        * **shipping_address** (optional) – Shipping address in case an event is
+                          shippable. It is used in fraud prevention. |br|
+                          Example:
+                          ``'475 Valencia St, 2nd Floor, San Francisco, 94103, USA'``.
+                        * **shipping_zip** (optional) – Same as **shipping_address**. Include only
+                          zip here. |br|
+                          Example: ``94103``.
+
+  **customer**          A person who issued an event:
+
+                        * **email**. (required) |br|
+                          Example: ``'customer@example.com'``.
+                        * **first_name** (optional). |br|
+                          Example: ``'John'``.
+                        * **last_name** (optional) |br|
+                          Example: ``'Smith'``.
+                        * **traffic_source** (optional) - specific
+                          :ref:`Traffic Source <advanced_features/segments>` value
+                          that helps to distinguish different points of integration. |br|
+                          Example: ``'facebook'``.
+
+  **campaign_tags**     Campaign tags are used to manually choose which campaign to show
+                        once the event has been tracked successfully (optional).
+
+                        Each Talkable campaign supports multiple tags, you can list them
+                        as an array: ``['tag1', 'tag2']``.
+
+                        You can control campaign tags inside Campaign Rules. Each
+                        Talkable campaign can have different tags.
+
+                        Alternatively, you can use
+                        :ref:`Campaign Placements <campaigns/campaign_placements>`
+                        feature to set up routing in your Talkable Dashboard instead
+                        of controlling it through the JS integration on your end. Campaign
+                        Placements are easy to change, no code changes are needed on your
+                        end.
+
+  **custom_properties** Custom key-value data that can be attached to a person
+                        (optional). It can be used for segmentation for example: you can
+                        code up custom criteria to show relevant campaigns to
+                        each segment. Alternatively, custom properties can be used for an
+                        advanced referral reward logics. Any valid JS object is allowed.
+                        Object value should always be a string.
+
+                        Example: ``{ key1: 'value1', key2: 'true' }``.
+                        :ref:`Learn more <advanced_features/passing_custom_data>`.
+
+  ===================== =================================================================
diff --git a/source/advanced_features/facebook_login_share.rst b/source/advanced_features/facebook_login_share.rst
index a29154cb4..22411713a 100644
--- a/source/advanced_features/facebook_login_share.rst
+++ b/source/advanced_features/facebook_login_share.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate Facebook Login & Share with your Talkable system for enhanced user authentication and social sharing. Follow our step-by-step guide to enable the app, configure Facebook App IDs, and streamline users login and sharing processes.
+  :description: Integrate Facebook Login & Share with your Talkable system for enhanced user authentication and social sharing. Follow our step-by-step guide to enable the app, configure Facebook App IDs, and streamline users login and sharing processes.
 
 Facebook Login & Share
 ======================
@@ -13,15 +13,15 @@ Overview
 This documentation provides a comprehensive guide on connecting your Facebook App for Login & Share in Talkable.
 
 .. note::
-   In case you don't have the Talkable Facebook app installed, users can still log in and share via Facebook, but Talkable's default Facebook app will be used.
+  In case you don't have the Talkable Facebook app installed, users can still log in and share via Facebook, but Talkable's default Facebook app will be used.
 
 Prerequisites
 -------------
 
 Before you begin, ensure you have the following:
 
-   - Access to the Facebook Developer Console.
-   - A Facebook App ID.
+- Access to the Facebook Developer Console.
+- A Facebook App ID.
 
 Integration Steps
 -----------------
@@ -82,4 +82,4 @@ Additional Resources
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/advanced_features/file_encryption.rst b/source/advanced_features/file_encryption.rst
index 1d47ae910..444d427c8 100644
--- a/source/advanced_features/file_encryption.rst
+++ b/source/advanced_features/file_encryption.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This is a public key encryption program that has become the most popular standard for email encryption.
+  :description: This is a public key encryption program that has become the most popular standard for email encryption.
 
 File Encryption
 ===============
@@ -27,14 +27,14 @@ Here is a command to do it:
 
 .. code-block:: shell
 
-   curl https://d2jjzw81hqbuqv.cloudfront.net/integration/talkable_public_key.asc | gpg --import
+  curl https://d2jjzw81hqbuqv.cloudfront.net/integration/talkable_public_key.asc | gpg --import
 
 To check that the Talkable public key importing was done right, make sure that
 the next command is successful:
 
 .. code-block:: shell
 
-   gpg --list-keys dev@talkable.com
+  gpg --list-keys dev@talkable.com
 
 Encrypting
 ----------
@@ -43,7 +43,7 @@ To encrypt data, you can use the following syntax:
 
 .. code-block:: shell
 
-   gpg --encrypt --sign --armor -r dev@talkable.com name_of_file
+  gpg --encrypt --sign --armor -r dev@talkable.com name_of_file
 
 This encrypts data using the Talkable public key and signs it with your own
 private key to guarantee that it is coming from you. Encrypted files will have the
@@ -53,8 +53,8 @@ as well.
 
 .. note::
 
-   You should include a second ``"-r"`` recipient with your own email address if
-   you want to be able to read the encrypted message.
+  You should include a second ``"-r"`` recipient with your own email address if
+  you want to be able to read the encrypted message.
 
 Decrypting
 ----------
@@ -63,10 +63,10 @@ To decrypt a file simply call GPG on it:
 
 .. code-block:: shell
 
-   gpg file_name.asc
+  gpg file_name.asc
 
 .. _How To Use GPG to Encrypt and Sign Messages: https://www.digitalocean.com/community/tutorials/how-to-use-gpg-to-encrypt-and-sign-messages#set-up-gpg-keys
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/google_login.rst b/source/advanced_features/google_login.rst
index 1eb30d1d3..31d36c5a5 100644
--- a/source/advanced_features/google_login.rst
+++ b/source/advanced_features/google_login.rst
@@ -13,7 +13,7 @@ Overview
 This documentation provides a comprehensive guide on integrating the Google Sign-In app into your Talkable system. By enabling this app, users can sign in using their Google accounts, enhancing security and reducing login friction.
 
 .. note::
-   In case you don't have the Talkable Google Sign-In app installed, users can still log in via Google in your Campaign, but Talkable credentials will be used for the OAuth flow.
+  In case you don't have the Talkable Google Sign-In app installed, users can still log in via Google in your Campaign, but Talkable credentials will be used for the OAuth flow.
 
 Prerequisites
 -------------
@@ -85,5 +85,4 @@ Additional Resources
 - OAuth 2.0 Documentation: https://developers.google.com/identity/protocols/oauth2
 
 .. note::
-   For detailed examples and advanced usage, refer to the official Google OAuth 2.0 documentation.
-
+  For detailed examples and advanced usage, refer to the official Google OAuth 2.0 documentation.
diff --git a/source/advanced_features/multi_currency.rst b/source/advanced_features/multi_currency.rst
index dc1dfa53b..a48f2b95d 100644
--- a/source/advanced_features/multi_currency.rst
+++ b/source/advanced_features/multi_currency.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable supports working with multiple currencies within the same site.
+  :description: Talkable supports working with multiple currencies within the same site.
 
 Multi-currency
 ==============
@@ -15,9 +15,8 @@ rewards based on the preferred currency. Every purchase and/or event should have
 The dashboard and reports can be filtered by currencies, and the values can be converted to a currency of your choice.
 
 .. note::
-
-   Please contact your Customer Success Manager to enable multi-currency. Note that in this mode,
-   the integration should pass currency data with every purchase.
+  Please contact your Customer Success Manager to enable multi-currency. Note that in this mode,
+  the integration should pass currency data with every purchase.
 
 Passing currency with the purchase or event
 -------------------------------------------
@@ -59,35 +58,34 @@ with the currency pre-selected:
 
 .. code-block:: javascript
 
-   _talkableq.push(['authenticate_customer', {
-     email: '',
-     currency: 'AUD' // Currency should be an international 3-letter code as defined by the ISO 4217 standard
-   }]);
+  _talkableq.push(['authenticate_customer', {
+    email: '',
+    currency: 'AUD' // Currency should be an international 3-letter code as defined by the ISO 4217 standard
+  }]);
 
 Currency can also be provided directly in any of the following function calls,
 overriding the `authenticate_customer` data:
 
-  - `register_affiliate`
-  - `register_purchase`
-  - `register_event`
+- `register_affiliate`
+- `register_purchase`
+- `register_event`
 
 For example:
 
 .. code-block:: javascript
 
-   var _purchase_data = {
-     purchase: {
-       order_number: '',
-       subtotal: '',
-       currency_iso_code: 'AUD' // currency of the purchase
-     },
-     currency: 'AUD', // preferred currency of the person, used to show suitable incentive information in the campaign
-   };
-   _talkableq.push(['register_purchase', _purchase_data]);
+  var _purchase_data = {
+    purchase: {
+      order_number: '',
+      subtotal: '',
+      currency_iso_code: 'AUD' // currency of the purchase
+    },
+    currency: 'AUD', // preferred currency of the person, used to show suitable incentive information in the campaign
+  };
+  _talkableq.push(['register_purchase', _purchase_data]);
 
 .. note::
-
-   Passing `currency` is available in integration version 5.2.1 or higher.
+  Passing `currency` is available in integration version 5.2.1 or higher.
 
 Currencies on dashboard
 -----------------------
@@ -100,10 +98,9 @@ Dashboard tiles have two helpful configuration options for multi-currency setup:
 .. image:: /_static/img/advanced_features/multi_currency_dashboard_tile.png
 
 .. note::
-
-   Conversion rate for a specific currency is actualized daily (data taken from
-   `open exchange rates <https://openexchangerates.org>`_) and cached for the accuracy of historical data.
-   So a purchase amount is converted according to its creation date's conversion rate.
+  Conversion rate for a specific currency is actualized daily (data taken from
+  `open exchange rates <https://openexchangerates.org>`_) and cached for the accuracy of historical data.
+  So a purchase amount is converted according to its creation date's conversion rate.
 
 Currencies in reports
 ---------------------
@@ -120,8 +117,7 @@ Available options in **Metrics Aggregation Report**:
   :width: 300
 
 .. note::
-
-   If a currency to convert to is not specified, the site currency is used for conversion.
+  If a currency to convert to is not specified, the site currency is used for conversion.
 
 Available options in **Purchases** and **Events** reports:
 
@@ -129,10 +125,9 @@ Available options in **Purchases** and **Events** reports:
 * select a currency to convert the amounts to
 
 .. note::
-
-   The options list in the currency filter consists of all the currencies passed to Talkable
-   along with the purchases/events. If you can't find a currency in the list, it means Talkable never received
-   a purchase/event with such currency.
+  The options list in the currency filter consists of all the currencies passed to Talkable
+  along with the purchases/events. If you can't find a currency in the list, it means Talkable never received
+  a purchase/event with such currency.
 
 Shopify discounts
 -----------------
@@ -160,4 +155,4 @@ This adjustment process minimizes manual updates for merchants and prevents disc
 
 .. note::
 
-    Our product uses **own exchange rates**, which are updated automatically every 24 hours
+  Our product uses **own exchange rates**, which are updated automatically every 24 hours
\ No newline at end of file
diff --git a/source/advanced_features/name_sharing.rst b/source/advanced_features/name_sharing.rst
index 84e960065..8f1450666 100644
--- a/source/advanced_features/name_sharing.rst
+++ b/source/advanced_features/name_sharing.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable allows the Advocates to share referral offers by their names.
+  :description: Talkable allows the Advocates to share referral offers by their names.
 
 Name Sharing
 ============
@@ -51,17 +51,17 @@ If you don't have the localization in your campaign code, you can add it manuall
 
 .. code-block:: liquid
 
-   {% assign advocate_share_page_channel_personal_name = "advocate_share_page_channel_personal_name" | localize: trait: "boolean", default: "Disabled" %}
+  {% assign advocate_share_page_channel_personal_name = "advocate_share_page_channel_personal_name" | localize: trait: "boolean", default: "Disabled" %}
 
 There can be multiple Advocate campaigns, as well as multiple Friend campaigns.
 Upon a reward claim by a Friend, the newest offer from the respective Advocate will be matched.
 
 .. important::
-   Make sure to set up both advocate and friend incentives in the Advocate campaign. The Claim by Name campaign
-   does not hold any incentive configuration and only serves to show a claim widget.
+  Make sure to set up both advocate and friend incentives in the Advocate campaign. The Claim by Name campaign
+  does not hold any incentive configuration and only serves to show a claim widget.
 
 .. note::
-   All advocate and friend metrics are counted toward the Advocate campaign.
+  All advocate and friend metrics are counted toward the Advocate campaign.
 
 Inline Widget
 -------------
@@ -72,18 +72,18 @@ the different offers and only one Claim by Name campaign, which will serve all t
 In the rules of the Claim by Name campaign there is an option to make the floating widget inline. This can be done in the Rules of the campaign:
 
 .. image:: /_static/img/advanced_features/name_sharing_inline_widget_1.png
-   :alt: Inline widget option
+  :alt: Inline widget option
 
 After that the campaign will be embedded in the page:
 
 .. image:: /_static/img/advanced_features/name_sharing_inline_widget_2.png
-   :alt: Inline widget
+  :alt: Inline widget
 
 Once you enabled “Inline Widget”, ask client to add the following code for the inline campaign (container):
 
 .. code-block:: html
 
-   <div id=’talkable-claim-by-name’></div>
+  <div id=’talkable-claim-by-name’></div>
 
 Without adding this code, the campaign won’t be visible.
 
@@ -100,7 +100,7 @@ If Shopify theme uses shopping cart as a dynamic widget, you can integrate Claim
 
 .. code-block:: html
 
-   <div id=’talkable-claim-by-name’></div>
+  <div id=’talkable-claim-by-name’></div>
 
 Interactions with the personal name-share link
 ----------------------------------------------
diff --git a/source/advanced_features/params_encryption.rst b/source/advanced_features/params_encryption.rst
index d1cb94c6b..db37a7c4d 100644
--- a/source/advanced_features/params_encryption.rst
+++ b/source/advanced_features/params_encryption.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: It is possible to encrypt Advocate, Friend, and Loyalty member emails on back-end if you want to provide additional security.
+  :description: It is possible to encrypt Advocate, Friend, and Loyalty member emails on back-end if you want to provide additional security.
 
 Params Encryption
 =================
@@ -24,30 +24,29 @@ Also it’s possible to pass encrypted email as a GET parameter (e.g. for CTA li
 point to standalone invite page). But to do that encrypted email should be **URL-encoded**.
 
 .. note::
-
-   It’s recommended to use `Optimal Asymmetric Encryption Padding (OAEP)`_ padding scheme together with RSA encryption.
+  It’s recommended to use `Optimal Asymmetric Encryption Padding (OAEP)`_ padding scheme together with RSA encryption.
 
 Ruby Example
 ------------
 
 .. code-block:: ruby
 
-   require 'openssl'
-   require 'base64'
+  require 'openssl'
+  require 'base64'
 
-   def key
-     @key ||= begin
-       key_content = File.read('talkable_your_site_slug_public_key.pem')
-       OpenSSL::PKey::RSA.new(key_content)
-     end
-   end
+  def key
+    @key ||= begin
+      key_content = File.read('talkable_your_site_slug_public_key.pem')
+      OpenSSL::PKey::RSA.new(key_content)
+    end
+  end
 
-   def encode_param_for_talkable(param)
-     encrypted_param = key.public_encrypt(param, OpenSSL::PKey::RSA::PKCS1_OAEP_PADDING)
-     Base64.strict_encode64(encrypted_param)
-   end
+  def encode_param_for_talkable(param)
+    encrypted_param = key.public_encrypt(param, OpenSSL::PKey::RSA::PKCS1_OAEP_PADDING)
+    Base64.strict_encode64(encrypted_param)
+  end
 
-   puts encode_param_for_talkable("email_to_encrypt@example.com")
+  puts encode_param_for_talkable("email_to_encrypt@example.com")
 
 Java Example
 ------------
@@ -60,126 +59,125 @@ This example uses `Bouncy Castle library`_ and has been tested on:
 that can be downloaded from `Bouncy Castle Latest Releases`_.
 
 .. note::
-
-   Please note that loading a Security Provider and a key into memory takes more time than encrypting.
-   So it is recommended to store the key in memory instead of loading it each time to avoid performance overhead.
+  Please note that loading a Security Provider and a key into memory takes more time than encrypting.
+  So it is recommended to store the key in memory instead of loading it each time to avoid performance overhead.
 
 .. code-block:: java
 
-   import javax.crypto.BadPaddingException;
-   import javax.crypto.Cipher;
-   import javax.crypto.IllegalBlockSizeException;
-   import java.io.FileReader;
-   import java.io.IOException;
-   import java.security.*;
-   import java.util.Base64;
-
-   import org.bouncycastle.asn1.x509.SubjectPublicKeyInfo;
-   import org.bouncycastle.jce.provider.BouncyCastleProvider;
-   import org.bouncycastle.openssl.PEMParser;
-   import org.bouncycastle.openssl.jcajce.JcaPEMKeyConverter;
-
-   public class EncryptionDemo {
-       static class ParamEncryptor {
-           private Cipher cipher;
-           private Key publicKey;
-
-           private void initPublicKey() throws IOException {
-               PEMParser pemParser = new PEMParser(new FileReader("talkable_your_site_slug_public_key.pem"));
-               JcaPEMKeyConverter converter = new JcaPEMKeyConverter().setProvider("BC");
-               SubjectPublicKeyInfo publicKeyInfo = (SubjectPublicKeyInfo) pemParser.readObject();
-               publicKey = converter.getPublicKey(publicKeyInfo);
-           }
-
-           private void initCipher() throws GeneralSecurityException {
-               cipher = Cipher.getInstance("RSA/ECB/OAEPPadding", "BC");
-               cipher.init(Cipher.ENCRYPT_MODE, publicKey);
-           }
-
-           public ParamEncryptor() throws IOException, GeneralSecurityException {
-               initPublicKey();
-               initCipher();
-           }
-
-           public String encryptParam(String param) throws BadPaddingException, IllegalBlockSizeException {
-               byte[] input = param.getBytes();
-               byte[] cipherText = cipher.doFinal(input);
-               byte[] encodedBytes = Base64.getEncoder().encode(cipherText);
-               return new String(encodedBytes);
-           }
-       }
-
-       static ParamEncryptor paramEncryptor;
-
-       static {
-           Security.addProvider(new BouncyCastleProvider());
-           try {
-               paramEncryptor = new ParamEncryptor();
-           } catch (IOException | GeneralSecurityException e) {
-               e.printStackTrace();
-           }
+  import javax.crypto.BadPaddingException;
+  import javax.crypto.Cipher;
+  import javax.crypto.IllegalBlockSizeException;
+  import java.io.FileReader;
+  import java.io.IOException;
+  import java.security.*;
+  import java.util.Base64;
+
+  import org.bouncycastle.asn1.x509.SubjectPublicKeyInfo;
+  import org.bouncycastle.jce.provider.BouncyCastleProvider;
+  import org.bouncycastle.openssl.PEMParser;
+  import org.bouncycastle.openssl.jcajce.JcaPEMKeyConverter;
+
+  public class EncryptionDemo {
+      static class ParamEncryptor {
+          private Cipher cipher;
+          private Key publicKey;
+
+          private void initPublicKey() throws IOException {
+              PEMParser pemParser = new PEMParser(new FileReader("talkable_your_site_slug_public_key.pem"));
+              JcaPEMKeyConverter converter = new JcaPEMKeyConverter().setProvider("BC");
+              SubjectPublicKeyInfo publicKeyInfo = (SubjectPublicKeyInfo) pemParser.readObject();
+              publicKey = converter.getPublicKey(publicKeyInfo);
+          }
+
+          private void initCipher() throws GeneralSecurityException {
+              cipher = Cipher.getInstance("RSA/ECB/OAEPPadding", "BC");
+              cipher.init(Cipher.ENCRYPT_MODE, publicKey);
+          }
+
+          public ParamEncryptor() throws IOException, GeneralSecurityException {
+              initPublicKey();
+              initCipher();
+          }
+
+          public String encryptParam(String param) throws BadPaddingException, IllegalBlockSizeException {
+              byte[] input = param.getBytes();
+              byte[] cipherText = cipher.doFinal(input);
+              byte[] encodedBytes = Base64.getEncoder().encode(cipherText);
+              return new String(encodedBytes);
+          }
+      }
+
+      static ParamEncryptor paramEncryptor;
+
+      static {
+          Security.addProvider(new BouncyCastleProvider());
+          try {
+              paramEncryptor = new ParamEncryptor();
+          } catch (IOException | GeneralSecurityException e) {
+              e.printStackTrace();
+          }
+      }
+
+      public static String encryptParam(String param) throws BadPaddingException, IllegalBlockSizeException {
+          return paramEncryptor.encryptParam(param);
+      }
+
+      public static void main(String[] args) throws Exception {
+          String email = "email_to_encrypt@example.com";
+          System.out.println(encryptParam(email));
        }
-
-       public static String encryptParam(String param) throws BadPaddingException, IllegalBlockSizeException {
-           return paramEncryptor.encryptParam(param);
-       }
-
-       public static void main(String[] args) throws Exception {
-           String email = "email_to_encrypt@example.com";
-           System.out.println(encryptParam(email));
-       }
-   }
+  }
 
 Node.js Example
 ---------------
 
 .. code-block:: js
 
-   const fs = require('fs');
-   const crypto = require('crypto');
+  const fs = require('fs');
+  const crypto = require('crypto');
 
-   // Read the public key from file
-   const publicKey = fs.readFileSync('talkable_your_site_slug_public_key.pem', 'utf8');
+  // Read the public key from file
+  const publicKey = fs.readFileSync('talkable_your_site_slug_public_key.pem', 'utf8');
 
-   const encryptData = (data) => {
-     const encryptedData = crypto.publicEncrypt(
-       {
-         key: publicKey,
-         padding: crypto.constants.RSA_PKCS1_OAEP_PADDING,
-         oaepHash: 'sha1',
-       },
-       Buffer.from(data)
-     );
-     return encryptedData.toString('base64');
-   };
+  const encryptData = (data) => {
+    const encryptedData = crypto.publicEncrypt(
+      {
+        key: publicKey,
+        padding: crypto.constants.RSA_PKCS1_OAEP_PADDING,
+        oaepHash: 'sha1',
+      },
+      Buffer.from(data)
+    );
+    return encryptedData.toString('base64');
+  };
 
-   // Example usage
-   const encryptedEmail = encryptData('email_to_encrypt@example.com');
-   console.log('Encrypted email:', encryptedEmail);
+  // Example usage
+  const encryptedEmail = encryptData('email_to_encrypt@example.com');
+  console.log('Encrypted email:', encryptedEmail);
 
 Front-end Part
 --------------
 
 .. important::
-   Do not use params encryption for :ref:`Talkable backend API <api_v2/origins>`.
+  Do not use params encryption for :ref:`Talkable backend API <api_v2/origins>`.
 
-   Params encryption is only for JS integration.
+  Params encryption is only for JS integration.
 
 Please modify the front-end using this pseudo code example:
 
 .. code-block:: html
 
-   <script>
-     _talkableq.push(['authenticate_customer', {
-       email: '<%= to_json(TalkableEncryptionService.encrypt(current_user.email)) %>',
-       phone_number: '<%= to_json(TalkableEncryptionService.encrypt(current_user.phone_number)) %>',
-       first_name: '<%= to_json(current_user.first_name) %>',
-       last_name: '<%= to_json(current_user.last_name) %>',
-       person_custom_properties: {
-         secret: '<%= to_json(TalkableEncryptionService.encrypt(current_user.secret)) %>'
-       }
-     }]);
-   </script>
+  <script>
+    _talkableq.push(['authenticate_customer', {
+      email: '<%= to_json(TalkableEncryptionService.encrypt(current_user.email)) %>',
+      phone_number: '<%= to_json(TalkableEncryptionService.encrypt(current_user.phone_number)) %>',
+      first_name: '<%= to_json(current_user.first_name) %>',
+      last_name: '<%= to_json(current_user.last_name) %>',
+      person_custom_properties: {
+        secret: '<%= to_json(TalkableEncryptionService.encrypt(current_user.secret)) %>'
+      }
+    }]);
+  </script>
 
 .. _Talkable Public Key: https://d2jjzw81hqbuqv.cloudfront.net/integration/talkable_public_key.pem
 .. _Bouncy Castle Library: https://www.bouncycastle.org
diff --git a/source/advanced_features/passing_custom_data.rst b/source/advanced_features/passing_custom_data.rst
index 0f3b5db64..72e015b16 100644
--- a/source/advanced_features/passing_custom_data.rst
+++ b/source/advanced_features/passing_custom_data.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The custom properties variable allows you to transfer any custom data to Talkable as a collection of key-value pairs.
+  :description: The custom properties variable allows you to transfer any custom data to Talkable as a collection of key-value pairs.
 
 Pass Custom User Data
 =====================
@@ -17,7 +17,7 @@ across all Campaign Views.
 
 .. raw:: html
 
-   <h2>How to set</h2>
+  <h2>How to set</h2>
 
 **Initialization script**
 
@@ -57,33 +57,33 @@ The properties you add to the initialization script will be automatically passed
 
 .. note::
 
-    The values you pass in the ``custom_properties`` have to be JSON Key-Value pairs themselves,
-    meaning that complex nested data structures cannot be passed through.
-    Property names (e.g. ``eye_color``) can contain lowercase letters, numbers and ``_`` only and cannot begin with a number.
+  The values you pass in the ``custom_properties`` have to be JSON Key-Value pairs themselves,
+  meaning that complex nested data structures cannot be passed through.
+  Property names (e.g. ``eye_color``) can contain lowercase letters, numbers and ``_`` only and cannot begin with a number.
 
 .. raw:: html
 
-   <h2>How to use</h2>
+  <h2>How to use</h2>
 
 To access ``custom_properties`` in Talkable, use:
 
 .. code-block:: liquid
 
-   {{ advocate_custom_properties }}
-   {{ friend_custom_properties }}
-   {{ member_info.custom_properties }}
+  {{ advocate_custom_properties }}
+  {{ friend_custom_properties }}
+  {{ member_info.custom_properties }}
 
 Key-Value pairs can be referenced calling the desired data key, such as:
 
 .. code-block:: liquid
 
-   {{ advocate_custom_properties.eye_color }}
+  {{ advocate_custom_properties.eye_color }}
 
 .. note::
 
-    Any ``custom_properties`` data passed through is tied to the |advocate|, |friend|, or |loyalty_member|.
-    If Talkable receives a custom property that was previously defined for the user, the property gets overwritten with a new value.
+  Any ``custom_properties`` data passed through is tied to the |advocate|, |friend|, or |loyalty_member|.
+  If Talkable receives a custom property that was previously defined for the user, the property gets overwritten with a new value.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/personal_coupon_sharing.rst b/source/advanced_features/personal_coupon_sharing.rst
index be0c91a09..c3c1cecb9 100644
--- a/source/advanced_features/personal_coupon_sharing.rst
+++ b/source/advanced_features/personal_coupon_sharing.rst
@@ -1,7 +1,7 @@
 .. _advanced_features/personal_coupon_sharing:
 
 .. meta::
-   :description: By clicking on the share link each Friend sees the discount on the Friend claim page.
+  :description: By clicking on the share link each Friend sees the discount on the Friend claim page.
 
 Advocate Personal Coupon Sharing
 ================================
@@ -129,4 +129,4 @@ Any UTF8 characters are allowed (including spaces).
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/phone_number_gating.rst b/source/advanced_features/phone_number_gating.rst
index af6c99d10..be12c36a6 100644
--- a/source/advanced_features/phone_number_gating.rst
+++ b/source/advanced_features/phone_number_gating.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Phone number feature allows you to collect customers' phone numbers inside your campaigns and use them for promotions.
+  :description: Phone number feature allows you to collect customers' phone numbers inside your campaigns and use them for promotions.
 
 Phone number gating
 ===================
diff --git a/source/advanced_features/product_items.rst b/source/advanced_features/product_items.rst
index a8a450bb9..78bfaa7c1 100644
--- a/source/advanced_features/product_items.rst
+++ b/source/advanced_features/product_items.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can also add product-specific tracking to Talkable’s campaign. This will let your customers share specific items they purchased.
+  :description: You can also add product-specific tracking to Talkable’s campaign. This will let your customers share specific items they purchased.
 
 Including Product Items
 =======================
@@ -17,5 +17,5 @@ Below is an example with product items passed along with purchase data (notice F
 
 .. note::
 
-   All product items are included into Purchase details inside Purchases report.
-   This information is helpful for debugging.
+  All product items are included into Purchase details inside Purchases report.
+  This information is helpful for debugging.
diff --git a/source/advanced_features/referrals_approval.rst b/source/advanced_features/referrals_approval.rst
index 066cb81d2..4f921bd5a 100644
--- a/source/advanced_features/referrals_approval.rst
+++ b/source/advanced_features/referrals_approval.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The approvals process helps automatically detect fake new user accounts. Cheaters won’t get through the system.
+  :description: The approvals process helps automatically detect fake new user accounts. Cheaters won’t get through the system.
 
 Referrals Approval
 ==================
diff --git a/source/advanced_features/reg_ex.rst b/source/advanced_features/reg_ex.rst
index 1e03ae270..64f3b08f1 100644
--- a/source/advanced_features/reg_ex.rst
+++ b/source/advanced_features/reg_ex.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable allows setting up of campaign placement “Shown on” / “Hidden on” criteria in two formats: relative match and regular expression.
+  :description: Talkable allows setting up of campaign placement “Shown on” / “Hidden on” criteria in two formats: relative match and regular expression.
 
 Setting up Campaign Placement criteria
 ======================================
@@ -133,4 +133,4 @@ formats:
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/report_password_protection.rst b/source/advanced_features/report_password_protection.rst
index e900542a5..88376fd50 100644
--- a/source/advanced_features/report_password_protection.rst
+++ b/source/advanced_features/report_password_protection.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: To protect sensitive information, all exported reports are password protected by default.
+  :description: To protect sensitive information, all exported reports are password protected by default.
 
 Report Password Protection
 ==========================
@@ -17,14 +17,14 @@ After the report generation, the user will receive an email with a link to downl
 ZIP file and a password to unzip it.
 
 .. image:: /_static/img/password_protected_report_email.png
-   :alt: Password Protected Report
+  :alt: Password Protected Report
 
 To disable password protection in reports, you can turn off this option in the site settings:
 
 .. image:: /_static/img/password_protected_toggle.png
-   :alt: Password Protected Toggle
+  :alt: Password Protected Toggle
 
 .. note::
 
-   Do not turn off password protection unnecessarily because this setting
-   exists for protection reports data from hacker attacks.
+  Do not turn off password protection unnecessarily because this setting
+  exists for protection reports data from hacker attacks.
diff --git a/source/advanced_features/rybbon.rst b/source/advanced_features/rybbon.rst
index f42109ef3..283398bb2 100644
--- a/source/advanced_features/rybbon.rst
+++ b/source/advanced_features/rybbon.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate Rybbon with your Talkable system to generate gift claim links and manage campaign-specific rewards.
+  :description: Integrate Rybbon with your Talkable system to generate gift claim links and manage campaign-specific rewards.
 
 Rybbon
 ======
@@ -13,7 +13,7 @@ Overview
 This documentation provides a guide on integrating the Rybbon campaign with your Talkable system. By enabling this feature, you can generate gift claim links for users and customize reward amounts based on campaign settings.
 
 .. note::
-   Rybbon app must be installed and enabled for this integration to work.
+  Rybbon app must be installed and enabled for this integration to work.
 
 Functionality
 -------------
@@ -29,7 +29,7 @@ Example Usage
 
    .. code-block:: liquid
 
-      {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon }}
+     {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon }}
 
    This returns a link similar to:
    `https://www.rybbon.net/redeem.php?claimcode=ee645de47765bdbede751c8c6f08a619`
@@ -40,7 +40,7 @@ Allows setting a custom reward amount for Rybbon campaigns with variable denomin
 
 .. code-block:: liquid
 
-   {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
+  {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
 
 Limitations
 -----------
@@ -50,4 +50,4 @@ Limitations
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/advanced_features/segments.rst b/source/advanced_features/segments.rst
index bf249f1c7..f37d8e6e1 100644
--- a/source/advanced_features/segments.rst
+++ b/source/advanced_features/segments.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: While driving traffic to one of your campaigns, you can include a traffic source parameter as a URL query string. This will help to segment your reporting.
+  :description: While driving traffic to one of your campaigns, you can include a traffic source parameter as a URL query string. This will help to segment your reporting.
 
 Segments
 ========
@@ -20,32 +20,32 @@ criteria in there:
 
 .. code-block:: html
 
-   {% assign available_items = "sku1,sku2" | split: "," %}
-   {% assign user_items = advocate_origin.products | map: "product_id" %}
-   {% assign result = false %}
+  {% assign available_items = "sku1,sku2" | split: "," %}
+  {% assign user_items = advocate_origin.products | map: "product_id" %}
+  {% assign result = false %}
 
-   {% for available_item in available_items %}
-     {% for user_item in user_items %}
-       {% if user_item == available_item %}
-         {% assign result = true %}
-         {% break %}
-       {% endif %}
-     {% endfor %}
-   {% endfor %}
+  {% for available_item in available_items %}
+    {% for user_item in user_items %}
+      {% if user_item == available_item %}
+        {% assign result = true %}
+        {% break %}
+      {% endif %}
+    {% endfor %}
+  {% endfor %}
 
-   {{ result }}
+  {{ result }}
 
 Now only those customers who purchased a product with SKU of "SKU_GOES_HERE" will see a Campaign.
 The Campaign won’t show for any other product purchased.
 
 .. note::
 
-   In order to use this Campaign Join Criteria you need to make sure that the SKU numbers are passed
-   throught the integration first of all. To do that you need to go into Reports
-   (top header navigation) → Purchases → Click on "Details" link of any purchase and make sure there is "Product Id"
-   column with a valid "Product ID" value in place.
-   If there is no such column or it is blank you cannot use this feature unless you pass the following instructions
-   :ref:`Including Product Items <advanced_features/product_items>`.
+  In order to use this Campaign Join Criteria you need to make sure that the SKU numbers are passed
+  throught the integration first of all. To do that you need to go into Reports
+  (top header navigation) → Purchases → Click on "Details" link of any purchase and make sure there is "Product Id"
+  column with a valid "Product ID" value in place.
+  If there is no such column or it is blank you cannot use this feature unless you pass the following instructions
+  :ref:`Including Product Items <advanced_features/product_items>`.
 
 Please |contact_us| if you have any questions.
 
@@ -82,27 +82,26 @@ Example of usage with `register_purchase`:
 
 Example of usage with `authenticate_customer`:
 
- .. code-block:: javascript
+.. code-block:: javascript
 
-       window._talkableq.push(['authenticate_customer', {
-         email: '', // Email of the customer. Example: 'customer@example.com'
-         first_name: '', // First name of the customer. Example: 'John'
-         last_name: '', // Last name of the customer. Example: 'Doe'
-         traffic_source: '', // The source of the traffic driven to the campaign. Example: 'facebook'
-         segment1: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-         segment2: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-         segment3: '' // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-       }]);
+  window._talkableq.push(['authenticate_customer', {
+    email: '', // Email of the customer. Example: 'customer@example.com'
+    first_name: '', // First name of the customer. Example: 'John'
+    last_name: '', // Last name of the customer. Example: 'Doe'
+    traffic_source: '', // The source of the traffic driven to the campaign. Example: 'facebook'
+    segment1: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+    segment2: '', // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+    segment3: '' // Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+  }]);
 
 In this example, `segment1`, `segment2`, and `segment3` attributes are passed through `authenticate_customer` to enable segmentation without requiring an Origin creation.
 
 .. note::
 
-   Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
+  Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
 
 This approach simplifies custom data handling for customers, allowing for unified data across various methods and optimizing segmentation management without additional calls.
 
 .. container:: hidden
 
-   .. toctree::
-
+  .. toctree::
diff --git a/source/advanced_features/shopify_coupons_auto_apply.rst b/source/advanced_features/shopify_coupons_auto_apply.rst
index 55c5d065c..5bf06ebd3 100644
--- a/source/advanced_features/shopify_coupons_auto_apply.rst
+++ b/source/advanced_features/shopify_coupons_auto_apply.rst
@@ -17,31 +17,31 @@ This method involves including the discount code in the URL. This way, when a cu
 
    .. code-block:: liquid
 
-      {{ site_setup.url }}
-      {% if coupon.code %}
-        /discount/{{ coupon.code }}?redirect=!!! YOUR CURRENT URL !!!
-      {% endif %}
+     {{ site_setup.url }}
+     {% if coupon.code %}
+       /discount/{{ coupon.code }}?redirect=!!! YOUR CURRENT URL !!!
+     {% endif %}
 
    Result example:
 
    .. code-block:: liquid
 
-       {{ site_setup.url }}
-       {% if coupon.code %}
-         /discount/{{ coupon.code }}?redirect={{ site_setup.url }}&
-       {% else %}
-         ?
-       {% endif %}
-       utm_source=talkable
-       &utm_medium={{ sharing_channel }}
-       &utm_content={{ campaign_setup.name | encode_query_argument }}
-       &utm_campaign={{ campaign_setup.id }}
-       &tkbl_cvuuid={{ visitor_uuid }}
-       &talkable_visitor_offer_id={{ friend_offer.id }}
+     {{ site_setup.url }}
+     {% if coupon.code %}
+       /discount/{{ coupon.code }}?redirect={{ site_setup.url }}&
+     {% else %}
+       ?
+     {% endif %}
+     utm_source=talkable
+     &utm_medium={{ sharing_channel }}
+     &utm_content={{ campaign_setup.name | encode_query_argument }}
+     &utm_campaign={{ campaign_setup.id }}
+     &tkbl_cvuuid={{ visitor_uuid }}
+     &talkable_visitor_offer_id={{ friend_offer.id }}
 
    .. image:: /_static/img/shopify/auto_apply/friend_destination_url.png
-      :alt: Friend destination url
-      :class: is-minimal
+     :alt: Friend destination url
+     :class: is-minimal
 
    **Breakdown:**
 
@@ -59,21 +59,21 @@ This method involves including the discount code in the URL. This way, when a cu
 
    .. code-block:: liquid
 
-       {{ site_setup.url }}
-       {% if coupon.code %}
-         /discount/{{ coupon.code }}?redirect={{ site_setup.url }}&
-       {% else %}
-         ?
-       {% endif %}
-       tkbl_cvuuid={{ visitor_uuid }}
+     {{ site_setup.url }}
+     {% if coupon.code %}
+       /discount/{{ coupon.code }}?redirect={{ site_setup.url }}&
+     {% else %}
+       ?
+     {% endif %}
+     tkbl_cvuuid={{ visitor_uuid }}
 
    .. image:: /_static/img/shopify/auto_apply/advocate_destination_url.png
-      :alt: Advocate destination url
-      :class: is-minimal
+     :alt: Advocate destination url
+     :class: is-minimal
 
    .. note::
 
-      Advocate Reward Paid email should use `{{ proceed_to_advocate_destination_url }}` variable
+     Advocate Reward Paid email should use `{{ proceed_to_advocate_destination_url }}` variable
 
 
 Method 2: Coupon application via client-side library integration
@@ -85,31 +85,31 @@ Here's the code snippet to include:
 
 .. code-block:: javascript
 
-   //Auto apply coupon code
-   _talkableq.push(['gleam_reward', {
-     callback: function(coupon) {
-       if (window.jQuery) {
-         $("body").on("submit", "form[action='/cart']", function(data) {
-             $('<input />').attr('type', 'hidden')
-               .attr('name', "discount")
-               .attr('value', coupon)
-               .appendTo($("form[action='/cart']"));
-             return true;
-         });
-       } else {
-         var forms = document.getElementsByTagName('form'),
-             discount = document.createElement('input');
-         discount.type = 'hidden';
-         discount.name = 'discount';
-         discount.value = coupon;
-         for (var i = 0; i < forms.length; i++) {
-           if (forms[i].action.indexOf('/cart') !== -1) {
-             forms[i].appendChild(discount);
-           }
-         }
-       }
-     }
-   }]);
+  //Auto apply coupon code
+  _talkableq.push(['gleam_reward', {
+    callback: function(coupon) {
+      if (window.jQuery) {
+        $("body").on("submit", "form[action='/cart']", function(data) {
+            $('<input />').attr('type', 'hidden')
+              .attr('name', "discount")
+              .attr('value', coupon)
+              .appendTo($("form[action='/cart']"));
+            return true;
+        });
+      } else {
+        var forms = document.getElementsByTagName('form'),
+            discount = document.createElement('input');
+        discount.type = 'hidden';
+        discount.name = 'discount';
+        discount.value = coupon;
+        for (var i = 0; i < forms.length; i++) {
+          if (forms[i].action.indexOf('/cart') !== -1) {
+            forms[i].appendChild(discount);
+          }
+        }
+      }
+    }
+  }]);
 
 **Breakdown:**
 
@@ -119,4 +119,4 @@ If jQuery is available, it sets up an event listener for the form submission. Wh
 
 If jQuery is not available, it does essentially the same thing using vanilla JavaScript. It loops through all forms in the document, and if it finds one with an action containing '/cart', it appends the hidden discount input field.
 
-These methods will allow the coupon to be automatically applied when a customer adds a product to their cart and proceeds to checkout.
\ No newline at end of file
+These methods will allow the coupon to be automatically applied when a customer adds a product to their cart and proceeds to checkout.
diff --git a/source/advanced_features/single_sign_on.rst b/source/advanced_features/single_sign_on.rst
index 1d70168e8..189d4325b 100644
--- a/source/advanced_features/single_sign_on.rst
+++ b/source/advanced_features/single_sign_on.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable fully supports the SAML v2.0 standard, making it easy to add more security and convenience to your Talkable program.
+  :description: Talkable fully supports the SAML v2.0 standard, making it easy to add more security and convenience to your Talkable program.
 
 Single Sign-On (SSO)
 ====================
@@ -25,19 +25,19 @@ Here is some basic terminology to help you in this guide:
 
 .. container:: ptable
 
-   ======================== =========================================================================================
-   Parameter                Description
-   ======================== =========================================================================================
-   Identity Provider (IdP)  The software/service that verifies the identity of your users. For example, Okta, OneLogin,
-                            Active Directory, etc.
-   Service Provider (SP)    Talkable.
-   Metadata URL             URL for the provider’s metadata. Both the IdP and the SP should have a Metadata URL.
-   Issuer (Entity ID)       A unique string that identifies the provider issuing a SAML request. According to the SAML
-                            specification, the string should be a URL, though not all providers respect this.
-                            Not required by all providers.
-   Consumer URL             The Talkable (SP) URL that will receive SAML requests from your IdP.
-   IdP SSO Target URL       The IdP URL that will receive SAML requests from Talkable (the SP).
-   ======================== =========================================================================================
+  ======================== =========================================================================================
+  Parameter                Description
+  ======================== =========================================================================================
+  Identity Provider (IdP)  The software/service that verifies the identity of your users. For example, Okta, OneLogin,
+                           Active Directory, etc.
+  Service Provider (SP)    Talkable.
+  Metadata URL             URL for the provider’s metadata. Both the IdP and the SP should have a Metadata URL.
+  Issuer (Entity ID)       A unique string that identifies the provider issuing a SAML request. According to the SAML
+                           specification, the string should be a URL, though not all providers respect this.
+                           Not required by all providers.
+  Consumer URL             The Talkable (SP) URL that will receive SAML requests from your IdP.
+  IdP SSO Target URL       The IdP URL that will receive SAML requests from Talkable (the SP).
+  ======================== =========================================================================================
 
 Automatic Configuration
 -----------------------
@@ -78,7 +78,7 @@ Once you've configured SSO, you can test it as followed:
 
 .. raw:: html
 
-   <h4>IdP-initiated SSO</h4>
+  <h4>IdP-initiated SSO</h4>
 
 1. Log out of Talkable
 2. Log in to your IdP (e.g. Okta, OneLogin, etc.)
@@ -86,7 +86,7 @@ Once you've configured SSO, you can test it as followed:
 
 .. raw:: html
 
-   <h4>SP-initiated SSO</h4>
+  <h4>SP-initiated SSO</h4>
 
 1. Log out of Talkable
 2. Visit the SP-Initiated SSO URL (provided on the SSO configuration page in Talkable)
@@ -95,4 +95,4 @@ Once you've configured SSO, you can test it as followed:
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/subscribing_to_events.rst b/source/advanced_features/subscribing_to_events.rst
index 5bba0a677..af42ae98a 100644
--- a/source/advanced_features/subscribing_to_events.rst
+++ b/source/advanced_features/subscribing_to_events.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable JS integration script embeds Talkable campaign as an iframe.
+  :description: Talkable JS integration script embeds Talkable campaign as an iframe.
 
 Subscribing To Iframe Events
 ============================
@@ -54,4 +54,4 @@ Talkable campaigns are equipped with the following set of events:
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/track_methods.rst b/source/advanced_features/track_methods.rst
index 901d2b3e9..2f0349a78 100644
--- a/source/advanced_features/track_methods.rst
+++ b/source/advanced_features/track_methods.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Tracking referrals feature lets you track each referral.
+  :description: Tracking referrals feature lets you track each referral.
 
 Referral Tracking Methods
 #########################
@@ -25,7 +25,7 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Manually Generated</h2>
+  <h2>Manually Generated</h2>
 
 - Only applies when the referral is made from Talkable admin pages.
 - Has the top priority because it forces the referral to be made without
@@ -33,14 +33,14 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Force Manually Generated</h2>
+  <h2>Force Manually Generated</h2>
 
 - Only applies when the referral is made from Talkable admin pages.
 - This is a Manually Generated Referral with skipped all fraud policy rules and incentive criterias.
 
 .. raw:: html
 
-   <h2>Sticky Advocate</h2>
+  <h2>Sticky Advocate</h2>
 
 - Only available for sites that have this feature enabled in the site settings.
 - Designed for case where a single person can only be referred once, so that
@@ -54,7 +54,7 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Coupon</h2>
+  <h2>Coupon</h2>
 
 - Friend used the coupon code he received through a Friend offer.
 - Only applies to campaigns that are giving a single use coupon as a reward to a
@@ -62,13 +62,13 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Cookie</h2>
+  <h2>Cookie</h2>
 
 - Friend used the same browser session as when clicking the referral link.
 
 .. raw:: html
 
-   <h2>Web Cookie</h2>
+  <h2>Web Cookie</h2>
 
 - Only applies to the iOS/Android Mobile SDKs.
 - Friend used the same browser session as when clicking the referral link.
@@ -78,21 +78,21 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Gated Email</h2>
+  <h2>Gated Email</h2>
 
 - Friend used the same email address as they entered on the claim page.
 - Only applies to campaigns that have Friend Signup feature enabled.
 
 .. raw:: html
 
-   <h2>Share Email</h2>
+  <h2>Share Email</h2>
 
 - Friend used the same email address in the Friend Share Email.
 - Only applies to offers shared by Email channel.
 
 .. raw:: html
 
-   <h2>IP Address</h2>
+  <h2>IP Address</h2>
 
 - Friend used the same IP address as when clicking the referral link.
 - Time limit: only applies when a Friend made a purchase or event within 1 hour
@@ -102,7 +102,7 @@ The list of tracking methods by their priority:
 
 .. raw:: html
 
-   <h2>Event Chain</h2>
+  <h2>Event Chain</h2>
 
 - Friend was already referred before and this is his subsequent event. In this
   case, this event is automatically attributed to the same Advocate as the
diff --git a/source/advanced_features/tremendous.rst b/source/advanced_features/tremendous.rst
index aab3dcfc1..1e0fb2a75 100644
--- a/source/advanced_features/tremendous.rst
+++ b/source/advanced_features/tremendous.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Reward advocates with gift cards provided by Tremendous.
+  :description: Reward advocates with gift cards provided by Tremendous.
 
 Tremendous Integration
 ######################
@@ -22,18 +22,18 @@ Tremendous integration consists of several parts:
      - An Advocate Referral Incentive with "Tremendous" reward type
 
        .. image:: /_static/img/advanced_features/tremendous_incentive.png
-          :width: 400
-          :alt: Creating a Tremendous Advocate Referral incentive
+         :width: 400
+         :alt: Creating a Tremendous Advocate Referral incentive
 
      - A :ref:`"tremendous" Liquid filter<tremendous_filter>` used in Reward Paid Email Page.
        The filter generates a claim link within the specified Tremendous campaign.
 
        .. code-block:: html
 
-          <!-- An example of the claim link leading to Tremendous -->
-          <a href="{{ 'KBBYF5Q64BL4' | tremendous }}" target="_blank" title="{{ cta_text }}">
-            {{ cta_text }}
-          </a>
+         <!-- An example of the claim link leading to Tremendous -->
+         <a href="{{ 'KBBYF5Q64BL4' | tremendous }}" target="_blank" title="{{ cta_text }}">
+           {{ cta_text }}
+         </a>
 
 **Contact us**
 
diff --git a/source/advanced_features/url_parameters.rst b/source/advanced_features/url_parameters.rst
index bda339fa0..bea1df9a6 100644
--- a/source/advanced_features/url_parameters.rst
+++ b/source/advanced_features/url_parameters.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable allows overriding some of the parameters right through URL query string.
+  :description: Talkable allows overriding some of the parameters right through URL query string.
 
 Using URL Parameters
 ====================
@@ -20,14 +20,14 @@ the page where Talkable campaign is integrated: http://example.com/share:
 
 .. code-block:: html
 
-   http://example.com/share?email=advocate%40example.com
+  http://example.com/share?email=advocate%40example.com
 
 Location parameters have higher priority than explicit parameters passed in the
 integration.
 
 .. note::
 
-   Don’t forget to escape URL parameters with URI parameter encoder.
+  Don’t forget to escape URL parameters with URI parameter encoder.
 
 .. container:: hidden
 
diff --git a/source/advanced_features/utm_tags.rst b/source/advanced_features/utm_tags.rst
index 78c008c5f..eb491f225 100644
--- a/source/advanced_features/utm_tags.rst
+++ b/source/advanced_features/utm_tags.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: While driving traffic to one of your campaigns, you can include a UTM Tags parameters as a URL query string. This will help to segment your reporting.
+  :description: While driving traffic to one of your campaigns, you can include a UTM Tags parameters as a URL query string. This will help to segment your reporting.
 
 UTM Tags
 ========
@@ -22,8 +22,8 @@ Example of usage:
 
 .. code-block:: text
 
-   https://example1.com/friends?refer=friends&utm_source=example_source&utm_medium=example_medium
+  https://example1.com/friends?refer=friends&utm_source=example_source&utm_medium=example_medium
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/advanced_features/white_labeling.rst b/source/advanced_features/white_labeling.rst
index 7e639f28c..660f7b3b5 100644
--- a/source/advanced_features/white_labeling.rst
+++ b/source/advanced_features/white_labeling.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable can be white-labeled so that links and URLs will point to your domain. Nobody will know how you created your referral program.
+  :description: Talkable can be white-labeled so that links and URLs will point to your domain. Nobody will know how you created your referral program.
 
 White-labeling
 ==============
@@ -134,13 +134,13 @@ To avoid that, you either need to:
 
   .. code-block::
 
-     v=spf1 include:mailgun.org include:_spf.google.com include:mail.zendesk.com include:_spf.salesforce.com ~all
+    v=spf1 include:mailgun.org include:_spf.google.com include:mail.zendesk.com include:_spf.salesforce.com ~all
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
 
-      white_labeling/aws_route53
-      white_labeling/shopify
-      white_labeling/godaddy
-      white_labeling/cloudflare
+     white_labeling/aws_route53
+     white_labeling/shopify
+     white_labeling/godaddy
+     white_labeling/cloudflare
diff --git a/source/advanced_features/white_labeling/aws_route53.rst b/source/advanced_features/white_labeling/aws_route53.rst
index 68b20d264..e6cf7bac7 100644
--- a/source/advanced_features/white_labeling/aws_route53.rst
+++ b/source/advanced_features/white_labeling/aws_route53.rst
@@ -1,14 +1,14 @@
 .. _advanced_features/white_labeling/aws_route53:
 
 .. meta::
-   :description: Learn how to add DNS records in AWS Route53 to enable white-labeling.
+  :description: Learn how to add DNS records in AWS Route53 to enable white-labeling.
 
 Adding DNS records in AWS Route53
 =================================
 
 .. note::
 
-   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
 
 #. Go to Hosted zones and select your main domain hosted zone (for instance, `example.com`).
 
diff --git a/source/advanced_features/white_labeling/cloudflare.rst b/source/advanced_features/white_labeling/cloudflare.rst
index f315898f3..f62adc633 100644
--- a/source/advanced_features/white_labeling/cloudflare.rst
+++ b/source/advanced_features/white_labeling/cloudflare.rst
@@ -1,14 +1,14 @@
 .. _advanced_features/white_labeling/cloudflare:
 
 .. meta::
-   :description: Learn how to add DNS records in Cloudflare to enable white-labeling.
+  :description: Learn how to add DNS records in Cloudflare to enable white-labeling.
 
 Adding DNS records in Cloudflare
 ================================
 
 .. note::
 
-   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
 
 `Cloudflare docs <https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records>`_
 
diff --git a/source/advanced_features/white_labeling/godaddy.rst b/source/advanced_features/white_labeling/godaddy.rst
index 5f762650f..b9f76bc66 100644
--- a/source/advanced_features/white_labeling/godaddy.rst
+++ b/source/advanced_features/white_labeling/godaddy.rst
@@ -1,21 +1,21 @@
 .. _advanced_features/white_labeling/godaddy:
 
 .. meta::
-   :description: Learn how to add DNS records in GoDaddy to enable white-labeling.
+  :description: Learn how to add DNS records in GoDaddy to enable white-labeling.
 
 Adding DNS records in GoDaddy
 =============================
 
 .. note::
 
-   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
 
 `GoDaddy docs <https://www.godaddy.com/help/manage-dns-records-680>`_
 
 .. note::
-   This instruction applies to domains that have GoDaddy name servers.
-   If you purchased a GoDaddy domain, but use other service's name servers,
-   you should add DNS records in the name server account.
+  This instruction applies to domains that have GoDaddy name servers.
+  If you purchased a GoDaddy domain, but use other service's name servers,
+  you should add DNS records in the name server account.
 
 #. Click **My Account** → **Domains**.
 
diff --git a/source/advanced_features/white_labeling/shopify.rst b/source/advanced_features/white_labeling/shopify.rst
index 88b295cda..1d1fc3d79 100644
--- a/source/advanced_features/white_labeling/shopify.rst
+++ b/source/advanced_features/white_labeling/shopify.rst
@@ -1,18 +1,18 @@
 .. _advanced_features/white_labeling/shopify:
 
 .. meta::
-   :description: Learn how to add DNS records in Shopify to enable white-labeling.
+  :description: Learn how to add DNS records in Shopify to enable white-labeling.
 
 Adding DNS records in Shopify
 =============================
 
 .. note::
-   The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
+  The instructions below use `subdomain.example.com` as an example of a custom domain where `example.com` is your domain.
 
 .. note::
-   This instruction applies to domains that are transferred to Shopify
-   or registered there in the first place.
-   Third-party domains connected to Shopify should be managed in respective domain registries.
+  This instruction applies to domains that are transferred to Shopify
+  or registered there in the first place.
+  Third-party domains connected to Shopify should be managed in respective domain registries.
 
 For delegated setup,
 
diff --git a/source/android_sdk.rst b/source/android_sdk.rst
index 018dba3af..9d2e5673b 100644
--- a/source/android_sdk.rst
+++ b/source/android_sdk.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable has an Android framework enabling you to use Talkable in Android apps.
+  :description: Talkable has an Android framework enabling you to use Talkable in Android apps.
 
 Talkable Android SDK
 ####################
@@ -25,10 +25,10 @@ Contents:
 
 .. toctree::
 
-   android_sdk/getting_started
-   android_sdk/integration
-   android_sdk/advanced
-   android_sdk/api
-   android_sdk/custom_deep_linking
-   android_sdk/testing
-   android_sdk/upgrade
+  android_sdk/getting_started
+  android_sdk/integration
+  android_sdk/advanced
+  android_sdk/api
+  android_sdk/custom_deep_linking
+  android_sdk/testing
+  android_sdk/upgrade
diff --git a/source/android_sdk/advanced.rst b/source/android_sdk/advanced.rst
index a7f61f3b9..5a99564b7 100644
--- a/source/android_sdk/advanced.rst
+++ b/source/android_sdk/advanced.rst
@@ -44,36 +44,36 @@ To use multiple site slugs (also known as IDs) in your application, follow these
 
    .. code-block:: xml
 
-      <application>
-          ...
-          <meta-data
-              android:name="tkbl-default-site-slug"
-              android:value="{{YOUR_DEFAULT_SITE_SLUG}}" />
-          ...
-      </application>
+     <application>
+         ...
+         <meta-data
+             android:name="tkbl-default-site-slug"
+             android:value="{{YOUR_DEFAULT_SITE_SLUG}}" />
+         ...
+     </application>
 
    or by passing it through ``Talkable.initialize`` in the ``Application``:
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
-      import android.app.Application;
+     import com.talkable.sdk.Talkable;
+     import android.app.Application;
 
-      public class App extends Application {
-          @Override
-          public void onCreate() {
-              super.onCreate();
-              Talkable.initialize(this, "your-default-site-slug");
-          }
-      }
+     public class App extends Application {
+         @Override
+         public void onCreate() {
+             super.onCreate();
+             Talkable.initialize(this, "your-default-site-slug");
+         }
+     }
 
    .. note::
 
-      You can set the site slug at any time after initialization in the following way:
+     You can set the site slug at any time after initialization in the following way:
 
       .. code-block:: java
 
-         Talkable.setSiteSlug("some-site-slug");
+        Talkable.setSiteSlug("some-site-slug");
 
    Make sure to add the credentials for this site inside the manifest file.
    Otherwise, an exception will be raised.
@@ -92,28 +92,28 @@ Overriding default behaviour
 
    .. code-block:: java
 
-      import com.talkable.sdk.TalkableOfferFragment;
+     import com.talkable.sdk.TalkableOfferFragment;
 
-      public class OverriddenTalkableOfferFragment extends TalkableOfferFragment {
-          @Override
-          public void copyToClipboard(String string) {
-              super.copyToClipboard(string);
+     public class OverriddenTalkableOfferFragment extends TalkableOfferFragment {
+         @Override
+         public void copyToClipboard(String string) {
+             super.copyToClipboard(string);
 
-              Toast.makeText(getActivity(), "Text copied!", Toast.LENGTH_LONG).show();
-          }
-      }
+             Toast.makeText(getActivity(), "Text copied!", Toast.LENGTH_LONG).show();
+         }
+     }
 
 2. Pass Class of an activity you want to run a fragment in and the overriden fragment to
    `Talkable.showOffer` call:
 
    .. code-block:: java
 
-      Talkable.showOffer(activity, affiliateMember, OverridenTalkableOfferFragment.class, new TalkableErrorCallback<TalkableOfferLoadException>() {
-          @Override
-          public void onError(TalkableOfferLoadException error) {
-              // Error handling. Note that it runs on non UI thread
-          }
-      });
+     Talkable.showOffer(activity, affiliateMember, OverridenTalkableOfferFragment.class, new TalkableErrorCallback<TalkableOfferLoadException>() {
+         @Override
+         public void onError(TalkableOfferLoadException error) {
+             // Error handling. Note that it runs on non UI thread
+         }
+     });
 
 .. _fragment_listener:
 
@@ -122,16 +122,16 @@ If you want to implement custom offer closing handling you should implement
 
 .. code-block:: java
 
-   import com.talkable.sdk.TalkableOfferFragment.TalkableOfferFragmentListener;
+  import com.talkable.sdk.TalkableOfferFragment.TalkableOfferFragmentListener;
 
-   public class MyActivity implements TalkableOfferFragmentListener {
-       ...
-       @Override
-       public void onOfferClosed() {
-           finish();
-       }
-       ...
-   }
+  public class MyActivity implements TalkableOfferFragmentListener {
+      ...
+      @Override
+      public void onOfferClosed() {
+          finish();
+      }
+      ...
+  }
 
 .. _using_fragment_directly:
 
@@ -150,30 +150,30 @@ To use ``TalkableOfferFragment`` directly, follow these steps:
 
 .. code-block:: java
 
-   AffiliateMember affiliateMember = new AffiliateMember();
-   ...
+  AffiliateMember affiliateMember = new AffiliateMember();
+  ...
 
-   Talkable.loadOffer(affiliateMember, new TalkableCallback<String, TalkableOfferLoadException>() {
-       // Note that it runs on non UI thread
-       @Override
-       public void onSuccess(String offerCode) {
-           TalkableOfferFragment fragment = TalkableOfferFragment.newInstance(offerCode);
-           myMethodToDisplayTalkableOfferFragment(fragment);
-       }
+  Talkable.loadOffer(affiliateMember, new TalkableCallback<String, TalkableOfferLoadException>() {
+      // Note that it runs on non UI thread
+      @Override
+      public void onSuccess(String offerCode) {
+          TalkableOfferFragment fragment = TalkableOfferFragment.newInstance(offerCode);
+          myMethodToDisplayTalkableOfferFragment(fragment);
+      }
 
-       @Override
-       public void onError(TalkableOfferLoadException error) {
-           // Error handling
-       }
-    );
+      @Override
+      public void onError(TalkableOfferLoadException error) {
+          // Error handling
+      }
+   );
 
 .. note::
 
-   Make sure to `handle configuration changes`_, as ``TalkableOfferFragment``
-   is built on top of ``WebView`` and restoring its state is up to you. If you
-   need to reinitialize a fragment, you don't need to call ``loadOffer`` again.
-   Simply store the ``offerCode`` and use it to create a new ``TalkableOfferFragment``
-   instance.
+  Make sure to `handle configuration changes`_, as ``TalkableOfferFragment``
+  is built on top of ``WebView`` and restoring its state is up to you. If you
+  need to reinitialize a fragment, you don't need to call ``loadOffer`` again.
+  Simply store the ``offerCode`` and use it to create a new ``TalkableOfferFragment``
+  instance.
 
 Native integration via API
 --------------------------
@@ -195,4 +195,4 @@ your Android application.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/api.rst b/source/android_sdk/api.rst
index 039e5d2ef..58902ed2d 100644
--- a/source/android_sdk/api.rst
+++ b/source/android_sdk/api.rst
@@ -51,45 +51,45 @@ You need to build `Origin` using one of examples below:
 
 .. code-block:: java
 
-    // Building customer, required for all types
-    String email = "advocate@example.com"; // Required
-    String idInYourApp = "a8db7683-0f7f-407e-8d12-af2d501035c8"; // Use unique identifier from your system, optional
-    String firstName = "John"; // Optional
-    String lastName = "Smith"; // Optional
-    Customer customer = new Customer(idInYourApp, firstName, lastName, email);
-
-    // Building AffiliateMember
-    AffiliateMember origin = new AffiliateMember();
-    origin.setCustomer(customer); // Required
-    origin.setCampaignTag("your-campaign-tag");
-
-    // Building Event
-    String eventNumber = "1"; // Required
-    String eventCategory = "event-category"; // Required
-    Double subtotal = 10.99; // Optional
-    String[] coupons = {"EXAMPLE-CODE"}; // Optional
-
-    Event origin = new Event(eventNumber, eventCategory, subtotal, coupons);
-    origin.setCustomer(customer); // Required
-    origin.setCampaignTag("your-campaign-tag");
-
-    // Build purchase
-    Double price = 10.99;
-    Integer quantity = 1;
-    String productId = "1";
-    Item item = new Item(subtotal, quantity, productId);
-    item.setTitle("Item Title"); // Optional
-    item.setUrl("https://site.com/product.html"); // Optional
-    item.setImageUrl("https://site.com/image.jpg"); // Optional
-
-    Double subtotal = price * quantity; // Required
-    String orderNumber = "123456"; // Required
-    String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
-
-    Purchase origin = new Purchase(subtotal, orderNumber, coupons);
-    origin.setCustomer(customer); // Required
-    origin.setCampaignTag("your-campaign-tag");
-    origin.addItem(item); // Optional
+  // Building customer, required for all types
+  String email = "advocate@example.com"; // Required
+  String idInYourApp = "a8db7683-0f7f-407e-8d12-af2d501035c8"; // Use unique identifier from your system, optional
+  String firstName = "John"; // Optional
+  String lastName = "Smith"; // Optional
+  Customer customer = new Customer(idInYourApp, firstName, lastName, email);
+
+  // Building AffiliateMember
+  AffiliateMember origin = new AffiliateMember();
+  origin.setCustomer(customer); // Required
+  origin.setCampaignTag("your-campaign-tag");
+
+  // Building Event
+  String eventNumber = "1"; // Required
+  String eventCategory = "event-category"; // Required
+  Double subtotal = 10.99; // Optional
+  String[] coupons = {"EXAMPLE-CODE"}; // Optional
+
+  Event origin = new Event(eventNumber, eventCategory, subtotal, coupons);
+  origin.setCustomer(customer); // Required
+  origin.setCampaignTag("your-campaign-tag");
+
+  // Build purchase
+  Double price = 10.99;
+  Integer quantity = 1;
+  String productId = "1";
+  Item item = new Item(subtotal, quantity, productId);
+  item.setTitle("Item Title"); // Optional
+  item.setUrl("https://site.com/product.html"); // Optional
+  item.setImageUrl("https://site.com/image.jpg"); // Optional
+
+  Double subtotal = price * quantity; // Required
+  String orderNumber = "123456"; // Required
+  String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
+
+  Purchase origin = new Purchase(subtotal, orderNumber, coupons);
+  origin.setCustomer(customer); // Required
+  origin.setCampaignTag("your-campaign-tag");
+  origin.addItem(item); // Optional
 
 API request
 ...........
@@ -99,17 +99,17 @@ If you have, you need call method like in the example below:
 
 .. code-block:: java
 
-    TalkableApi.createOrigin(origin, new Callback2<Origin, Offer>() {
-        @Override
-        public void onSuccess(Origin origin, Offer offer) {
-            // Process success
-        }
+  TalkableApi.createOrigin(origin, new Callback2<Origin, Offer>() {
+      @Override
+      public void onSuccess(Origin origin, Offer offer) {
+          // Process success
+      }
 
-        @Override
-        public void onError(ApiError error) {
-            // Process error
-        }
-    });
+      @Override
+      public void onError(ApiError error) {
+          // Process error
+      }
+  });
 
 .. _android-api-rewards:
 
@@ -120,37 +120,37 @@ This methods is used for retrieving rewards for user. Example:
 
 .. code-block:: java
 
-    TalkableApi.retrieveRewards(new Callback1<Reward[]>() {
-        @Override
-        public void onSuccess(Reward[] rewards) {
-            // Process success
-        }
+  TalkableApi.retrieveRewards(new Callback1<Reward[]>() {
+      @Override
+      public void onSuccess(Reward[] rewards) {
+          // Process success
+      }
 
-        @Override
-        public void onError(ApiError error) {
-            // Process error
-        }
-    });
+      @Override
+      public void onError(ApiError error) {
+          // Process error
+      }
+  });
 
 If you need get only rewards with some status or for other than user UUID,
 you need to pass this data to this method. Example:
 
 .. code-block:: java
 
-    Params params = new Params();
-    params.put("status", "Paid"); // Optional
-    params.put("visitor_uuid", "eb71e496-6567-41ec-a68c-49e96d101e0e"); // Some other uuid, optional
-    TalkableApi.retrieveRewards(params, new Callback1<Reward[]>() {
-        @Override
-        public void onSuccess(Reward[] rewards) {
-            // Process success
-        }
-
-        @Override
-        public void onError(ApiError error) {
-            // Process error
-        }
-    });
+  Params params = new Params();
+  params.put("status", "Paid"); // Optional
+  params.put("visitor_uuid", "eb71e496-6567-41ec-a68c-49e96d101e0e"); // Some other uuid, optional
+  TalkableApi.retrieveRewards(params, new Callback1<Reward[]>() {
+      @Override
+      public void onSuccess(Reward[] rewards) {
+          // Process success
+      }
+
+      @Override
+      public void onError(ApiError error) {
+          // Process error
+      }
+  });
 
 Retrieve offer
 --------------
@@ -159,18 +159,18 @@ This method is used to get offer details by it’s short code. Example:
 
 .. code-block:: java
 
-    String shortUrlCode = "ABCXYZ";
-    TalkableApi.retrieveOffer(shortUrlCode, new Callback1<Offer>() {
-        @Override
-        public void onSuccess(Offer newOffer) {
-            // Process success
-        }
+  String shortUrlCode = "ABCXYZ";
+  TalkableApi.retrieveOffer(shortUrlCode, new Callback1<Offer>() {
+      @Override
+      public void onSuccess(Offer newOffer) {
+          // Process success
+      }
 
-        @Override
-        public void onError(ApiError e) {
-            // Process error
-        }
-    });
+      @Override
+      public void onError(ApiError e) {
+          // Process error
+      }
+  });
 
 .. _android-api-sharing:
 
@@ -188,28 +188,28 @@ Use the ``createEmailShare`` method to share an offer via email.
 
 .. code-block:: java
 
-   String subject = "Email Subject"; // optional
-   String body = "Email custom message"; // optional
-   Boolean reminder = false; // whether Talkable should send a reminder email later; true by default; optional
-   ShareEmail email = new ShareEmail(subject, body, reminder); // optional
-
-   String recipients = "friend1@example.com,friend2@example.com"; // emails separated by commas; required
-   EmailOfferShare share = new EmailOfferShare(offer, recipients, email);
-   TalkableApi.createEmailShare(share, new Callback2<JsonElement, Reward>() {
-       @Override
-       public void onSuccess(JsonElement result, Reward reward) {
-           // Process success
-       }
-       @Override
-       public void onError(ApiError e) {
-           // Process error
-       }
-   });
+  String subject = "Email Subject"; // optional
+  String body = "Email custom message"; // optional
+  Boolean reminder = false; // whether Talkable should send a reminder email later; true by default; optional
+  ShareEmail email = new ShareEmail(subject, body, reminder); // optional
+
+  String recipients = "friend1@example.com,friend2@example.com"; // emails separated by commas; required
+  EmailOfferShare share = new EmailOfferShare(offer, recipients, email);
+  TalkableApi.createEmailShare(share, new Callback2<JsonElement, Reward>() {
+      @Override
+      public void onSuccess(JsonElement result, Reward reward) {
+          // Process success
+      }
+      @Override
+      public void onError(ApiError e) {
+          // Process error
+      }
+  });
 
 .. note::
 
-   ``JsonElement result`` from ``onSuccess(JsonElement result, Reward reward)``
-   contains data, described in |api_v2_share_via_email| under the ``result`` key
+  ``JsonElement result`` from ``onSuccess(JsonElement result, Reward reward)``
+  contains data, described in |api_v2_share_via_email| under the ``result`` key
 
 Social Share
 ............
@@ -218,19 +218,19 @@ Use the ``createSocialShare`` method to track a social share.
 
 .. code-block:: java
 
-   SharingChannel channel = SharingChannel.FACEBOOK; // required
-   SocialOfferShare share = new SocialOfferShare(offer, channel);
-   TalkableApi.createSocialShare(share, new Callback2<SocialOfferShare, Reward>() {
-       @Override
-       public void onSuccess(SocialOfferShare createdShare, Reward reward) {
-           // Process success
-       }
-       @Override
-       public void onError(ApiError e) {
-           // Process error
-       }
-   });
+  SharingChannel channel = SharingChannel.FACEBOOK; // required
+  SocialOfferShare share = new SocialOfferShare(offer, channel);
+  TalkableApi.createSocialShare(share, new Callback2<SocialOfferShare, Reward>() {
+      @Override
+      public void onSuccess(SocialOfferShare createdShare, Reward reward) {
+          // Process success
+      }
+      @Override
+      public void onError(ApiError e) {
+          // Process error
+      }
+  });
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/custom_deep_linking.rst b/source/android_sdk/custom_deep_linking.rst
index f8eed83e4..442026418 100644
--- a/source/android_sdk/custom_deep_linking.rst
+++ b/source/android_sdk/custom_deep_linking.rst
@@ -25,14 +25,14 @@ To use deep linking with Talkable campaigns, simply use your deep link URL as yo
 
 .. note::
 
-   If you have configured a custom Friend Destination URL for your campaign,
-   make sure the following GET parameters are present in the final URL:
-   ``?tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}``.
+  If you have configured a custom Friend Destination URL for your campaign,
+  make sure the following GET parameters are present in the final URL:
+  ``?tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}``.
 
-   All major deep linking providers support passing additional GET parameters
-   with the deep link. This functionality is used to pass the Friend's identifying
-   information to the Talkable SDK in your iOS app. To use this functionality with
-   Firebase, refer to this document: `Manually constructing a Dynamic Link URL`_.
+  All major deep linking providers support passing additional GET parameters
+  with the deep link. This functionality is used to pass the Friend's identifying
+  information to the Talkable SDK in your iOS app. To use this functionality with
+  Firebase, refer to this document: `Manually constructing a Dynamic Link URL`_.
 
 2. Pass deep linking params to the Talkable SDK
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -49,58 +49,58 @@ following types:
 
 .. code-block:: java
 
-   // For Branch.io
+  // For Branch.io
 
-   Branch.getInstance().initSession(new Branch.BranchReferralInitListener() {
-       @Override
-       public void onInitFinished(JSONObject referringParams, BranchError error) {
-           TalkableDeepLinking.track(referringParams);
-       }
-   }, this.getIntent().getData(), this);
+  Branch.getInstance().initSession(new Branch.BranchReferralInitListener() {
+      @Override
+      public void onInitFinished(JSONObject referringParams, BranchError error) {
+          TalkableDeepLinking.track(referringParams);
+      }
+  }, this.getIntent().getData(), this);
 
 .. note::
 
-   Most deep linking services provide additional parameters in the deep link
-   handler to indicate whether the app was installed on this device for the first
-   time, reinstalled or simply launched. You can use these params to register
-   installs only when desired conditions are met.
+  Most deep linking services provide additional parameters in the deep link
+  handler to indicate whether the app was installed on this device for the first
+  time, reinstalled or simply launched. You can use these params to register
+  installs only when desired conditions are met.
 
 .. code-block:: java
 
-   // For GetSocial
+  // For GetSocial
 
-   GetSocial.getReferralData(new FetchReferralDataCallback() {
-       @Override
-       public void onSuccess(@Nullable ReferralData referralData) {
-           if (referralData != null && referralData.isFirstMatch()) {
-               TalkableDeepLinking.track(referralData.getLinkParams().getStringValues());
-           }
-       }
+  GetSocial.getReferralData(new FetchReferralDataCallback() {
+      @Override
+      public void onSuccess(@Nullable ReferralData referralData) {
+          if (referralData != null && referralData.isFirstMatch()) {
+              TalkableDeepLinking.track(referralData.getLinkParams().getStringValues());
+          }
+      }
 
-       @Override
-       public void onFailure(GetSocialException error) {}
-   }
+      @Override
+      public void onFailure(GetSocialException error) {}
+  }
 
 .. code-block:: java
 
-   // For Firebase
-
-   FirebaseDynamicLinks.getInstance()
-       .getDynamicLink(getIntent())
-       .addOnSuccessListener(this, new OnSuccessListener<PendingDynamicLinkData>() {
-           @Override
-           public void onSuccess(PendingDynamicLinkData pendingDynamicLinkData) {
-               // Get deep link from result (may be null if no link is found)
-               Uri deepLink = null;
-               if (pendingDynamicLinkData != null) {
-                   deepLink = pendingDynamicLinkData.getLink();
-               }
-
-               if (deepLink != null) {
-                   TalkableDeepLinking.track(deepLink);
-               }
-           }
-       })
+  // For Firebase
+
+  FirebaseDynamicLinks.getInstance()
+      .getDynamicLink(getIntent())
+      .addOnSuccessListener(this, new OnSuccessListener<PendingDynamicLinkData>() {
+          @Override
+          public void onSuccess(PendingDynamicLinkData pendingDynamicLinkData) {
+              // Get deep link from result (may be null if no link is found)
+              Uri deepLink = null;
+              if (pendingDynamicLinkData != null) {
+                  deepLink = pendingDynamicLinkData.getLink();
+              }
+
+              if (deepLink != null) {
+                  TalkableDeepLinking.track(deepLink);
+              }
+          }
+      })
 
 Calling the ``TalkableDeepLinking.track()`` method will register the app
 installation event in Talkable and complete the referral cycle.
diff --git a/source/android_sdk/deep_linking.rst b/source/android_sdk/deep_linking.rst
index 218cc4149..60f8c0301 100644
--- a/source/android_sdk/deep_linking.rst
+++ b/source/android_sdk/deep_linking.rst
@@ -12,10 +12,10 @@ your Android app.
 
 .. note::
 
-   Credentials, mentioned in this document (``YOUR_SITE_SLUG``, ``YOUR_TALKABLE_PUBLIC_API_KEY``,
-   ``YOUR_GETSOCIAL_APP_ID``, ``YOUR_LINK_DOMAIN_PREFIX``), will be provided
-   with the document. Make sure to replace corresponding placeholders
-   in examples with the providen values.
+  Credentials, mentioned in this document (``YOUR_SITE_SLUG``, ``YOUR_TALKABLE_PUBLIC_API_KEY``,
+  ``YOUR_GETSOCIAL_APP_ID``, ``YOUR_LINK_DOMAIN_PREFIX``), will be provided
+  with the document. Make sure to replace corresponding placeholders
+  in examples with the providen values.
 
 Application Attributes
 ----------------------
@@ -39,37 +39,37 @@ Talkable SDK is distributed as an Android Library in ``aar`` format.
 
    .. note::
 
-      To do this, open import popup using *File* → *New* → *New Module* → *Import .JAR/.AAR Package*
-      and add Talkable SDK as a module dependency to your main module
+     To do this, open import popup using *File* → *New* → *New Module* → *Import .JAR/.AAR Package*
+     and add Talkable SDK as a module dependency to your main module
 
 2. Add Talkable SDK dependencies to ``build.gradle``:
 
    .. code-block:: groovy
 
-      dependencies {
-          ...
-          implementation 'com.squareup.okhttp3:okhttp:3.2.0'
-          implementation 'com.facebook.android:facebook-android-sdk:[4,5)'
-          implementation 'im.getsocial:getsocial-core:[6,7)@aar'
-          implementation 'com.android.installreferrer:installreferrer:1.0'
-          implementation 'com.google.code.gson:gson:2.8.0'
-          implementation 'com.android.support:support-v4:27.1.1'
-          implementation project(':talkable-sdk')
-          ...
-      }
+     dependencies {
+         ...
+         implementation 'com.squareup.okhttp3:okhttp:3.2.0'
+         implementation 'com.facebook.android:facebook-android-sdk:[4,5)'
+         implementation 'im.getsocial:getsocial-core:[6,7)@aar'
+         implementation 'com.android.installreferrer:installreferrer:1.0'
+         implementation 'com.google.code.gson:gson:2.8.0'
+         implementation 'com.android.support:support-v4:27.1.1'
+         implementation project(':talkable-sdk')
+         ...
+     }
 
 3. Add GetSocial Maven Repository to the list of project dependency
    repositories inside your top-level ``build.gradle``:
 
    .. code-block:: groovy
 
-      allprojects {
-          repositories {
-              ...
-              maven { url 'http://maven.getsocial.im/' }
-              ...
-          }
-      }
+     allprojects {
+         repositories {
+             ...
+             maven { url 'http://maven.getsocial.im/' }
+             ...
+         }
+     }
 
 Configure Manifest
 ------------------
@@ -81,84 +81,84 @@ Open your ``AndroidManifest.xml`` file and configure it by following next steps:
 
    .. code-block:: xml
 
-       <application>
-           ...
-           <meta-data
-               android:name="tkbl-api-key-YOUR_SITE_SLUG"
-               android:value="YOUR_TALKABLE_PUBLIC_API_KEY" />
-           ...
-       </application>
+     <application>
+         ...
+         <meta-data
+             android:name="tkbl-api-key-YOUR_SITE_SLUG"
+             android:value="YOUR_TALKABLE_PUBLIC_API_KEY" />
+         ...
+     </application>
 
 2. Specify GetSocial App ID as a meta-data inside the ``<application>`` tag:
 
    .. code-block:: xml
 
-      <application>
-          ...
-          <meta-data
-              android:name="im.getsocial.sdk.AppId"
-              android:value="YOUR_GETSOCIAL_APP_ID" />
-          ...
-      </application>
+     <application>
+         ...
+         <meta-data
+             android:name="im.getsocial.sdk.AppId"
+             android:value="YOUR_GETSOCIAL_APP_ID" />
+         ...
+     </application>
 
 3. Add Content Provider for GetSocial SDK auto initialization inside the
    ``<application>`` tag:
 
    .. code-block:: xml
 
-      <application>
-          ...
-          <provider
-              android:authorities="YOUR_GETSOCIAL_APP_ID.AutoInitSdkContentProvider"
-              android:exported="false"
-              android:enabled="true"
-              android:name="im.getsocial.sdk.AutoInitSdkContentProvider" />
-          ...
-      </application>
+     <application>
+         ...
+         <provider
+             android:authorities="YOUR_GETSOCIAL_APP_ID.AutoInitSdkContentProvider"
+             android:exported="false"
+             android:enabled="true"
+             android:name="im.getsocial.sdk.AutoInitSdkContentProvider" />
+         ...
+     </application>
 
 4. Configure Install Referrer Receiver as the *first* receiver for ``INSTALL_REFERRER``
    inside the ``<application>`` tag:
 
    .. code-block:: xml
 
-      <application>
-          ...
-          <receiver android:name="im.getsocial.sdk.invites.MultipleInstallReferrerReceiver"  android:exported="true">
-              <intent-filter>
-                  <action android:name="com.android.vending.INSTALL_REFERRER"/>
-              </intent-filter>
-          </receiver>
-          ...
-      </application>
+     <application>
+         ...
+         <receiver android:name="im.getsocial.sdk.invites.MultipleInstallReferrerReceiver"  android:exported="true">
+             <intent-filter>
+                 <action android:name="com.android.vending.INSTALL_REFERRER"/>
+             </intent-filter>
+         </receiver>
+         ...
+     </application>
 
 5. Add the following intent filter to the activity, that should be opened from the
    deep link, inside the corresponding tag:
 
    .. code-block:: xml
 
-      <activity>
-          ...
-         <intent-filter>
-             <action android:name="android.intent.action.VIEW"/>
+     <activity>
+         ...
+        <intent-filter>
+            <action android:name="android.intent.action.VIEW"/>
 
-             <category android:name="android.intent.category.DEFAULT"/>
-             <category android:name="android.intent.category.BROWSABLE"/>
+            <category android:name="android.intent.category.DEFAULT"/>
+            <category android:name="android.intent.category.BROWSABLE"/>
 
-             <data
-                 android:host="YOUR_GETSOCIAL_APP_ID"
-                 android:scheme="getsocial"/>
-         </intent-filter>
+            <data
+                android:host="YOUR_GETSOCIAL_APP_ID"
+                android:scheme="getsocial"/>
+        </intent-filter>
 
-         <intent-filter>
-             <action android:name="android.intent.action.VIEW" />
+        <intent-filter>
+            <action android:name="android.intent.action.VIEW" />
 
-             <category android:name="android.intent.category.DEFAULT" />
-             <category android:name="android.intent.category.BROWSABLE" />
+            <category android:name="android.intent.category.DEFAULT" />
+            <category android:name="android.intent.category.BROWSABLE" />
 
-             <data android:scheme="tkbl-YOUR_SITE_SLUG" />
-         </intent-filter>
-         ...
-      </activity>
+            <data android:scheme="tkbl-YOUR_SITE_SLUG" />
+        </intent-filter>
+        ...
+     </activity>
 
 6. Setup App Links for Android 6+. App Links (supported on Android 6.0
    (API level 23) and higher) allow the user to be taken directly to the app
@@ -169,17 +169,17 @@ Open your ``AndroidManifest.xml`` file and configure it by following next steps:
 
    .. code-block:: xml
 
-      <activity>
-          ...
-         <intent-filter android:autoVerify="true">
-             <action android:name="android.intent.action.VIEW" />
-             <category android:name="android.intent.category.DEFAULT" />
-             <category android:name="android.intent.category.BROWSABLE" />
-             <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX.gsc.im" />
-             <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX-gsalt.gsc.im" />
-         </intent-filter>
+     <activity>
          ...
-      </activity>
+        <intent-filter android:autoVerify="true">
+            <action android:name="android.intent.action.VIEW" />
+            <category android:name="android.intent.category.DEFAULT" />
+            <category android:name="android.intent.category.BROWSABLE" />
+            <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX.gsc.im" />
+            <data android:scheme="https" android:host="YOUR_LINK_DOMAIN_PREFIX-gsalt.gsc.im" />
+        </intent-filter>
+        ...
+     </activity>
 
 SDK Initialization
 ------------------
@@ -188,34 +188,34 @@ SDK Initialization
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
+     import com.talkable.sdk.Talkable;
 
-      public class App extends Application {
-          @Override
-          public void onCreate() {
-              super.onCreate();
-              Talkable.initialize(this);
-          }
-      }
+     public class App extends Application {
+         @Override
+         public void onCreate() {
+             super.onCreate();
+             Talkable.initialize(this);
+         }
+     }
 
    .. note::
 
-      Make sure to add your application class name as ``android:name`` parameter
-      of the ``<application>`` element in your manifest.
+     Make sure to add your application class name as ``android:name`` parameter
+     of the ``<application>`` element in your manifest.
 
 2. Call the ``Talkable.trackAppOpen`` method inside your main activity:
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
+     import com.talkable.sdk.Talkable;
 
-      public class MainActivity extends Activity {
-          @Override
-          public void onCreate(Bundle savedInstanceState) {
-              super.onCreate();
-              Talkable.trackAppOpen(this);
-          }
-      }
+     public class MainActivity extends Activity {
+         @Override
+         public void onCreate(Bundle savedInstanceState) {
+             super.onCreate();
+             Talkable.trackAppOpen(this);
+         }
+     }
 
 Requirements
 ------------
@@ -228,4 +228,4 @@ The SDK supports Android 4.1 and later.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/getting_started.rst b/source/android_sdk/getting_started.rst
index 0a44dce7b..03108fb68 100644
--- a/source/android_sdk/getting_started.rst
+++ b/source/android_sdk/getting_started.rst
@@ -14,21 +14,21 @@ Installation
 
    .. code-block:: groovy
 
-      allprojects {
-        repositories {
-          ...
-          maven { url 'https://jitpack.io' }
-        }
-      }
+     allprojects {
+       repositories {
+         ...
+         maven { url 'https://jitpack.io' }
+       }
+     }
 
 2. Add TalkableSDK as a dependency to your module's *build.gradle* file.
 
    .. code-block:: groovy
 
-      dependencies {
-        ...
-        implementation 'com.github.talkable:android-sdk:0.5.12'
-      }
+     dependencies {
+       ...
+       implementation 'com.github.talkable:android-sdk:0.5.12'
+     }
 
 .. _setup_credentials:
 
@@ -37,21 +37,21 @@ Installation
 
    .. code-block:: xml
 
-      <application>
-          ...
-          <meta-data
-              android:name="tkbl-api-key-{{YOUR_SITE_ID}}"
-              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-          ...
-      </application>
+     <application>
+         ...
+         <meta-data
+             android:name="tkbl-api-key-{{YOUR_SITE_ID}}"
+             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+         ...
+     </application>
 
    .. note::
 
-      You can locate your credentials inside Talkable site:
+     You can locate your credentials inside Talkable site:
 
-      - Select site and go to **Dashboard** → **Settings** → **Site Settings** → **Integrations**.
-        Find **API integration** section and there you will see your API Keys and Site ID (also known as Site slug).
-        Use only the *Public API Key* in your production application.
+     - Select site and go to **Dashboard** → **Settings** → **Site Settings** → **Integrations**.
+       Find **API integration** section and there you will see your API Keys and Site ID (also known as Site slug).
+       Use only the *Public API Key* in your production application.
 
 .. _deep_linking_scheme:
 
@@ -60,17 +60,17 @@ Installation
 
    .. code-block:: xml
 
-      <activity>
-          ...
-          <intent-filter>
-              <action android:name="android.intent.action.VIEW" />
+     <activity>
+         ...
+         <intent-filter>
+             <action android:name="android.intent.action.VIEW" />
 
-              <category android:name="android.intent.category.DEFAULT" />
-              <category android:name="android.intent.category.BROWSABLE" />
+             <category android:name="android.intent.category.DEFAULT" />
+             <category android:name="android.intent.category.BROWSABLE" />
 
-              <data android:scheme="tkbl-{{YOUR_SITE_ID}}" />
-          </intent-filter>
-      </activity>
+             <data android:scheme="tkbl-{{YOUR_SITE_ID}}" />
+         </intent-filter>
+     </activity>
 
 .. _main_activity_setup:
 
@@ -78,80 +78,80 @@ Installation
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
-      import android.app.Application;
+     import com.talkable.sdk.Talkable;
+     import android.app.Application;
 
-      public class App extends Application {
-          @Override
-          public void onCreate() {
-              super.onCreate();
-              Talkable.initialize(this);
-          }
-      }
+     public class App extends Application {
+         @Override
+         public void onCreate() {
+             super.onCreate();
+             Talkable.initialize(this);
+         }
+     }
 
    .. note::
 
-      Make sure to add your application class name as ``android:name`` parameter of
-      the ``<application>`` element in your manifest
+     Make sure to add your application class name as ``android:name`` parameter of
+     the ``<application>`` element in your manifest
 
 6. Call ``Talkable.trackAppOpen`` inside you main activity class, like this:
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
-      import android.app.Activity;
+     import com.talkable.sdk.Talkable;
+     import android.app.Activity;
 
-      public class MainActivity extends Activity {
-          @Override
-          public void onCreate(Bundle savedInstanceState) {
-              ...
+     public class MainActivity extends Activity {
+         @Override
+         public void onCreate(Bundle savedInstanceState) {
+             ...
 
-              Talkable.trackAppOpen(this);
-          }
-      }
+             Talkable.trackAppOpen(this);
+         }
+     }
 
 Here is an example of ``AndroidManifest.xml`` file (with ``"demo-site"`` site
 ID) you should setup after steps above:
 
   .. code-block:: xml
 
-     <?xml version="1.0" encoding="utf-8"?>
-     <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-         package="com.talkable.demo">
+    <?xml version="1.0" encoding="utf-8"?>
+    <manifest xmlns:android="http://schemas.android.com/apk/res/android"
+        package="com.talkable.demo">
 
-         <application
-             android:allowBackup="true"
-             android:icon="@mipmap/ic_launcher"
-             android:label="@string/app_name"
-             android:supportsRtl="true"
-             android:theme="@style/AppTheme"
-             android:name=".App">
-             <activity android:name=".MainActivity">
-                 <intent-filter>
-                     <action android:name="android.intent.action.MAIN" />
+        <application
+            android:allowBackup="true"
+            android:icon="@mipmap/ic_launcher"
+            android:label="@string/app_name"
+            android:supportsRtl="true"
+            android:theme="@style/AppTheme"
+            android:name=".App">
+            <activity android:name=".MainActivity">
+                <intent-filter>
+                    <action android:name="android.intent.action.MAIN" />
 
-                     <category android:name="android.intent.category.LAUNCHER" />
-                 </intent-filter>
+                    <category android:name="android.intent.category.LAUNCHER" />
+                </intent-filter>
 
-                 <intent-filter>
-                     <action android:name="android.intent.action.VIEW" />
+                <intent-filter>
+                    <action android:name="android.intent.action.VIEW" />
 
-                     <category android:name="android.intent.category.DEFAULT" />
-                     <category android:name="android.intent.category.BROWSABLE" />
+                    <category android:name="android.intent.category.DEFAULT" />
+                    <category android:name="android.intent.category.BROWSABLE" />
 
-                     <data android:scheme="tkbl-demo-site" />
-                 </intent-filter>
-             </activity>
+                    <data android:scheme="tkbl-demo-site" />
+                </intent-filter>
+            </activity>
 
-             <!-- Talkable -->
+            <!-- Talkable -->
 
-             <meta-data
-                 android:name="tkbl-api-key-demo-site"
-                 android:value="nacsc9XseW4Kxne6AaJ" />
+            <meta-data
+                android:name="tkbl-api-key-demo-site"
+                android:value="nacsc9XseW4Kxne6AaJ" />
 
-             <!-- End Talkable -->
-         </application>
-     </manifest>
+            <!-- End Talkable -->
+        </application>
+    </manifest>
 
 Your environment is all set up! Now you need to
 :ref:`integrate <android_sdk/integration>` the Talkable campaign piece.
@@ -165,4 +165,4 @@ The SDK supports Android 4.1 and later.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/integration.rst b/source/android_sdk/integration.rst
index 16b3a95b1..977b9c292 100644
--- a/source/android_sdk/integration.rst
+++ b/source/android_sdk/integration.rst
@@ -14,6 +14,6 @@ The SDK is installed and setup. Now you can integrate Standalone or/and Post Pur
 
    .. toctree::
 
-      Standalone Campaign <integration/standalone>
-      Post Purchase Campaign <integration/post_purchase>
-      Custom Events <integration/event>
+     Standalone Campaign <integration/standalone>
+     Post Purchase Campaign <integration/post_purchase>
+     Custom Events <integration/event>
diff --git a/source/android_sdk/integration/event.rst b/source/android_sdk/integration/event.rst
index c40c7e32c..afb9dbb1d 100644
--- a/source/android_sdk/integration/event.rst
+++ b/source/android_sdk/integration/event.rst
@@ -10,12 +10,12 @@ An Event has two required properties: event category and event number. Please re
 
 .. code-block:: java
 
-     String eventNumber = "ev123789"; //must be unique for given category
-     String eventCategory = "subscription_purchased";
+  String eventNumber = "ev123789"; //must be unique for given category
+  String eventCategory = "subscription_purchased";
 
-     Event event = new Event(eventNumber, eventCategory);
+  Event event = new Event(eventNumber, eventCategory);
 
-     TalkableApi.createOrigin(event, new Callback2<Origin, Offer>() {...});
+  TalkableApi.createOrigin(event, new Callback2<Origin, Offer>() {...});
 
 If you have a Talkable offer configured for this event, the Talkable campaign screen will be displayed as a result of calling the ``createOrigin`` method.
 
@@ -27,19 +27,19 @@ Customer data can be added to the registered event. Custom properties passed wit
 
 .. code-block:: java
 
-     String email = "advocate@example.com";
-     String firstName = "John";
-     String lastName = "Smith";
-     HashMap<String, String> customProperties = new HashMap<String, String>();
-     customProperties.put("property_key", "property_value");
-     Customer customer = new Customer(null, firstName, lastName, email, customProperties);
+  String email = "advocate@example.com";
+  String firstName = "John";
+  String lastName = "Smith";
+  HashMap<String, String> customProperties = new HashMap<String, String>();
+  customProperties.put("property_key", "property_value");
+  Customer customer = new Customer(null, firstName, lastName, email, customProperties);
 
-     String eventNumber = "ev123789";
-     String eventCategory = "subscription_purchased";
+  String eventNumber = "ev123789";
+  String eventCategory = "subscription_purchased";
 
-     Event event = new Event(eventNumber, eventCategory);
-     event.setCustomer(customer);
+  Event event = new Event(eventNumber, eventCategory);
+  event.setCustomer(customer);
 
-     TalkableApi.createOrigin(event, new Callback2<Origin, Offer>() {...});
+  TalkableApi.createOrigin(event, new Callback2<Origin, Offer>() {...});
 
 Please refer to the :ref:`Integrating Events <advanced_features/events>` page to learn more about event-based campaigns.
diff --git a/source/android_sdk/integration/post_purchase.rst b/source/android_sdk/integration/post_purchase.rst
index 0ca3ef434..24d410b8b 100644
--- a/source/android_sdk/integration/post_purchase.rst
+++ b/source/android_sdk/integration/post_purchase.rst
@@ -18,47 +18,47 @@ Here is an example of a Purchase capturing, this action should be triggered on t
 
 .. code-block:: java
 
-   import com.talkable.sdk.Talkable;
-   ...
-   Double price = 10.99;
-   Integer quantity = 1;
-   String productId = "1";
-   Item item = new Item(subtotal, quantity, productId);
-   item.setTitle("Item Title"); // Optional
-   item.setUrl("https://site.com/product.html"); // Optional
-   item.setImageUrl("https://site.com/image.jpg"); // Optional
-
-   Double subtotal = price * quantity; // Required
-   String orderNumber = "123456"; // Required
-   String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
-
-   HashMap<String, String> customProperties = new HashMap<String, String>();
-   customProperties.put("property_key", "property_value");
-
-   Customer customer = new Customer(email);
-   customer.setCustomProperties(customProperties);
-
-   Purchase purchase = new Purchase(subtotal, orderNumber, coupons);
-   purchase.setCustomer(customer); // Required
-   purchase.addItem(item); // Optional
-
-   String campaignTag = "android-post-purchase";
-   purchase.setCampaignTag(campaignTag); // Optional
-
-   Activity activity = this;
-   Talkable.showOffer(activity, purchase, new TalkableErrorCallback<TalkableOfferLoadException>() {
-       @Override
-       public void onError(TalkableOfferLoadException error) {
-           // Error handling. Note that it runs on non UI thread
-       }
-   });
+  import com.talkable.sdk.Talkable;
+  ...
+  Double price = 10.99;
+  Integer quantity = 1;
+  String productId = "1";
+  Item item = new Item(subtotal, quantity, productId);
+  item.setTitle("Item Title"); // Optional
+  item.setUrl("https://site.com/product.html"); // Optional
+  item.setImageUrl("https://site.com/image.jpg"); // Optional
+
+  Double subtotal = price * quantity; // Required
+  String orderNumber = "123456"; // Required
+  String[] coupons = {"EXAMPLE-CODE-1", "EXAMPLE-CODE-2"}; // Optional
+
+  HashMap<String, String> customProperties = new HashMap<String, String>();
+  customProperties.put("property_key", "property_value");
+
+  Customer customer = new Customer(email);
+  customer.setCustomProperties(customProperties);
+
+  Purchase purchase = new Purchase(subtotal, orderNumber, coupons);
+  purchase.setCustomer(customer); // Required
+  purchase.addItem(item); // Optional
+
+  String campaignTag = "android-post-purchase";
+  purchase.setCampaignTag(campaignTag); // Optional
+
+  Activity activity = this;
+  Talkable.showOffer(activity, purchase, new TalkableErrorCallback<TalkableOfferLoadException>() {
+      @Override
+      public void onError(TalkableOfferLoadException error) {
+          // Error handling. Note that it runs on non UI thread
+      }
+  });
 
 .. note::
 
-   If Post Purchase campaign does not show up when testing make sure you have it Live
-   on the Campaigns listing with `android-post-purchase` tag or the tag you specified
-   in `setCampaignTag`.
+  If Post Purchase campaign does not show up when testing make sure you have it Live
+  on the Campaigns listing with `android-post-purchase` tag or the tag you specified
+  in `setCampaignTag`.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/integration/standalone.rst b/source/android_sdk/integration/standalone.rst
index b072b19ca..64785f657 100644
--- a/source/android_sdk/integration/standalone.rst
+++ b/source/android_sdk/integration/standalone.rst
@@ -68,4 +68,4 @@ flow and show the :ref:`Advocate Share Form <campaigns/views/offers_show>`.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/testing.rst b/source/android_sdk/testing.rst
index 1bba47163..4f73f1c17 100644
--- a/source/android_sdk/testing.rst
+++ b/source/android_sdk/testing.rst
@@ -16,10 +16,10 @@ the app is launched.
 
 .. code-block:: java
 
-   String initialSiteId = null; // pass null to use the Site ID specified in your manifest
-   boolean debug = true;
+  String initialSiteId = null; // pass null to use the Site ID specified in your manifest
+  boolean debug = true;
 
-   Talkable.initialize(this, initialSiteId, debug, null);
+  Talkable.initialize(this, initialSiteId, debug, null);
 
 You can use the last param to pass a custom device ID, allowing you to switch between user identities manually. This way
 you can use a single device to pose as an Advocate or Friend and easily replicate various scenarios. The custom device ID
@@ -27,16 +27,16 @@ will be applied only if debug is set to `true`.
 
 .. code-block:: java
 
-   String initialSiteId = null;
-   boolean debug = true;
-   String customDeviceId = "qa-advocate-007";
+  String initialSiteId = null;
+  boolean debug = true;
+  String customDeviceId = "qa-advocate-007";
 
-   Talkable.initialize(this, initialSiteId, debug, customDeviceId);
+  Talkable.initialize(this, initialSiteId, debug, customDeviceId);
 
 .. warning::
 
-   Debug mode must be turned off for release builds. Leaving it enabled will break the referral cycle and expose you to fraud.
+  Debug mode must be turned off for release builds. Leaving it enabled will break the referral cycle and expose you to fraud.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/android_sdk/upgrade.rst b/source/android_sdk/upgrade.rst
index 64f4b898a..a7d57ac0f 100644
--- a/source/android_sdk/upgrade.rst
+++ b/source/android_sdk/upgrade.rst
@@ -88,38 +88,38 @@ To update from the previous version, please do following steps.
 
    .. code-block:: groovy
 
-      // From
-      compile 'com.google.code.gson:gson:2.7'
-      compile 'com.android.support:support-v4:25.3.1'
+     // From
+     compile 'com.google.code.gson:gson:2.7'
+     compile 'com.android.support:support-v4:25.3.1'
 
-      // To
-      compile 'com.google.code.gson:gson:2.8'
-      compile 'com.android.support:support-v4:26.1.0'
+     // To
+     compile 'com.google.code.gson:gson:2.8'
+     compile 'com.android.support:support-v4:26.1.0'
 
 2. Use ``showOffer`` functions with a callback parameter.
 
    .. code-block:: java
 
-      // From
-      showOffer(activity, origin);
+     // From
+     showOffer(activity, origin);
 
-      // To
-      showOffer(activity, origin, new TalkableErrorCallback<TalkableOfferLoadException>() {
-          @Override
-          public void onError(final TalkableOfferLoadException error) {
-              // Error handling. Note that it runs on non UI thread
-          }
-      });
+     // To
+     showOffer(activity, origin, new TalkableErrorCallback<TalkableOfferLoadException>() {
+         @Override
+         public void onError(final TalkableOfferLoadException error) {
+             // Error handling. Note that it runs on non UI thread
+         }
+     });
 
 3. Use ``Talkable.setSiteSlug`` functions without Context as a parameter.
 
    .. code-block:: java
 
-      // From
-      setSiteSlug(context, "site-slug");
+     // From
+     setSiteSlug(context, "site-slug");
 
-      // To
-      setSiteSlug("site-slug");
+     // To
+     setSiteSlug("site-slug");
 
 4. ``TalkableOfferFragmentListener`` interface implementation is optional now.
 
@@ -135,11 +135,11 @@ permission inside the manifest:
 
    .. code-block:: xml
 
-      <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-        package="com.android.app.myapp" >
-        <uses-permission android:name="android.permission.READ_CONTACTS" />
-        ...
-      </manifest>
+     <manifest xmlns:android="http://schemas.android.com/apk/res/android"
+       package="com.android.app.myapp" >
+       <uses-permission android:name="android.permission.READ_CONTACTS" />
+       ...
+     </manifest>
 
 0.4.1
 -----
@@ -173,62 +173,62 @@ To update from the previous version, please do following steps.
 
    .. code-block:: xml
 
-      <!-- From -->
-      <application>
-          ...
-          <meta-data
-              android:name="TalkableApiKey"
-              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-          <meta-data
-              android:name="TalkableSiteSlug"
-              android:value="{{YOUR_SITE_SLUG}}" />
-          ...
-      </application>
-
-      <!-- To -->
-      <application>
-          ...
-          <meta-data
-              android:name="tkbl-api-key-{{YOUR_SITE_SLUG}}"
-              android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
-          ...
-      </application>
+     <!-- From -->
+     <application>
+         ...
+         <meta-data
+             android:name="TalkableApiKey"
+             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+         <meta-data
+             android:name="TalkableSiteSlug"
+             android:value="{{YOUR_SITE_SLUG}}" />
+         ...
+     </application>
+
+     <!-- To -->
+     <application>
+         ...
+         <meta-data
+             android:name="tkbl-api-key-{{YOUR_SITE_SLUG}}"
+             android:value="{{YOUR_TALKABLE_PUBLIC_API_KEY}}" />
+         ...
+     </application>
 
 3. Initialize Talkable in the ``Application``.
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
-      import android.app.Application;
+     import com.talkable.sdk.Talkable;
+     import android.app.Application;
 
-      public class App extends Application {
-          @Override
-          public void onCreate() {
-              super.onCreate();
-              Talkable.initialize(this);
-          }
-      }
+     public class App extends Application {
+         @Override
+         public void onCreate() {
+             super.onCreate();
+             Talkable.initialize(this);
+         }
+     }
 
    .. note::
 
-      Make sure to add your application class name as ``android:name`` parameter of
-      the ``<application>`` element in your manifest
+     Make sure to add your application class name as ``android:name`` parameter of
+     the ``<application>`` element in your manifest
 
 4. Call ``Talkable.trackAppOpen`` inside you main activity class, like before.
 
    .. code-block:: java
 
-      import com.talkable.sdk.Talkable;
-      import android.app.Activity;
+     import com.talkable.sdk.Talkable;
+     import android.app.Activity;
 
-      public class MainActivity extends Activity {
-          @Override
-          public void onCreate(Bundle savedInstanceState) {
-              ...
+     public class MainActivity extends Activity {
+         @Override
+         public void onCreate(Bundle savedInstanceState) {
+             ...
 
-              Talkable.trackAppOpen(this);
-          }
-      }
+             Talkable.trackAppOpen(this);
+         }
+     }
 
 From this version defining of ``TalkableActivity`` and ``InstallReferrerReceiver``
 inside Android Manifest is not necessary.
@@ -286,4 +286,4 @@ It’s initial release, nothing to do.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/api_v2.rst b/source/api_v2.rst
index 86d944b18..eb0feddb2 100644
--- a/source/api_v2.rst
+++ b/source/api_v2.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Here you can learn about API. Choose the category you’re most interested in.
+  :description: Here you can learn about API. Choose the category you’re most interested in.
 
 API Reference
 #############
@@ -11,7 +11,7 @@ Contents:
 
 .. toctree::
 
-   api_v2/intro
-   api_v2/flow
-   api_v2/origins
-   api_v2/referrals
+  api_v2/intro
+  api_v2/flow
+  api_v2/origins
+  api_v2/referrals
diff --git a/source/api_v2/flow.rst b/source/api_v2/flow.rst
index 2de54d831..9830c9bba 100644
--- a/source/api_v2/flow.rst
+++ b/source/api_v2/flow.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This flow helps to integrate with Talkable via API for a default store or service.
+  :description: This flow helps to integrate with Talkable via API for a default store or service.
 
 Referral Program via API
 ========================
@@ -19,7 +19,7 @@ Each of these steps can be done individually or all together to achieve API inte
 
 .. note::
 
-   Offers created via API are not marked as shown and thus are not counted towards advocate impressions.
+  Offers created via API are not marked as shown and thus are not counted towards advocate impressions.
 
 Initial Origin
 --------------
diff --git a/source/api_v2/intro.rst b/source/api_v2/intro.rst
index 49e242a25..4888437cb 100644
--- a/source/api_v2/intro.rst
+++ b/source/api_v2/intro.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The Talkable API is built on HTTP. Our API is RESTful, returns JSON, and responds with standard HTTP response codes to indicate errors.
+  :description: The Talkable API is built on HTTP. Our API is RESTful, returns JSON, and responds with standard HTTP response codes to indicate errors.
 
 Introduction
 ============
@@ -22,33 +22,33 @@ https://www.talkable.com/api-docs/
 Click **Authorize** to log in with the `API key <Authentication_>`_:
 
 .. image:: /_static/img/swagger/authorize1.png
-   :alt: Authorize step 1
-   :class: is-minimal
+  :alt: Authorize step 1
+  :class: is-minimal
 
 Enter the `API key <Authentication_>`_ and click **Authorize** again:
 
 .. image:: /_static/img/swagger/authorize2.png
-   :alt: Authorize step 2
-   :class: is-minimal
+  :alt: Authorize step 2
+  :class: is-minimal
 
 Click **Close**. The Authorize lock icon changes to locked:
 
 .. image:: /_static/img/swagger/authorize3.png
-   :alt: Authorize step 3
-   :class: is-minimal
-   :width: 156 px
+  :alt: Authorize step 3
+  :class: is-minimal
+  :width: 156 px
 
 .. raw:: html
 
-   <h4>Actions</h4>
+  <h4>Actions</h4>
 
 For details about the API call, expand the API method for each call. To issue an
 API call from the Talkable API user interface, click **Try it out** for any
 method. Edit the Example Values in the request body and click **Execute**.
 
 .. image:: /_static/img/swagger/actions.png
-   :alt: Actions
-   :class: is-minimal
+  :alt: Actions
+  :class: is-minimal
 
 Authentication
 --------------
@@ -58,21 +58,21 @@ You can manage your API key in the Account Settings.
 
 .. warning:: Keep your API key secret!
 
-   You should not embed the API key within a web page and make Talkable API calls
-   within JavaScript running within a browser. Once someone has your API key, they
-   could create their own API calls.
+  You should not embed the API key within a web page and make Talkable API calls
+  within JavaScript running within a browser. Once someone has your API key, they
+  could create their own API calls.
 
 Authentication to the API is performed via Bearer authentication header.
 
 .. raw:: html
 
-   <h4>Example Request</h4>
+  <h4>Example Request</h4>
 
 .. code-block:: bash
 
-   curl 'https://www.talkable.com/api/v2/campaigns?site_slug=my-store' \
-     -H 'accept: application/json' \
-     -H 'Authorization: Bearer i9uil7nQgDjucCiTJu'
+  curl 'https://www.talkable.com/api/v2/campaigns?site_slug=my-store' \
+    -H 'accept: application/json' \
+    -H 'Authorization: Bearer i9uil7nQgDjucCiTJu'
 
 Response Format
 ---------------
@@ -84,7 +84,7 @@ envelope includes these common parts:
 
 .. code-block:: javascript
 
-   {"ok": true, "result": ...}
+  {"ok": true, "result": ...}
 
 Date Format
 -----------
@@ -95,7 +95,7 @@ This format is supported by most programming languages out of the box:
 
 .. code-block:: text
 
-   2022-02-16T02:43:58.797-07:00
+  2022-02-16T02:43:58.797-07:00
 
 Errors
 ------
@@ -105,7 +105,7 @@ Talkable API call:
 
 .. code-block:: javascript
 
-   {"ok": false, "error_message": "Message describing the error"}
+  {"ok": false, "error_message": "Message describing the error"}
 
 Most error messages that Talkable API will return are not meant to be shown to
 the user. We expect your service to gracefully handle errors and only show
@@ -115,19 +115,19 @@ Talkable returns standard HTTP response codes.
 
 .. container:: ptable
 
-   =================== ======================================================
-   Code                Description
-   =================== ======================================================
-   200, 201            Everything worked as expected
-   400                 Bad Request - Often missing a required parameter
-   401                 Unauthorized - No valid API key provided
-   404                 Not Found - The requested item doesn’t exist
-   422                 Unprocessable Entity - The requested create, update,
-                       or delete cannot be performed due to validation errors.
-                       |br| See the response body for more details.
-   429                 Too Many Requests
-   500, 502, 503, 504  Server Errors - Something is wrong on Talkable’s end
-   =================== ======================================================
+  =================== ======================================================
+  Code                Description
+  =================== ======================================================
+  200, 201            Everything worked as expected
+  400                 Bad Request - Often missing a required parameter
+  401                 Unauthorized - No valid API key provided
+  404                 Not Found - The requested item doesn’t exist
+  422                 Unprocessable Entity - The requested create, update,
+                      or delete cannot be performed due to validation errors.
+                      |br| See the response body for more details.
+  429                 Too Many Requests
+  500, 502, 503, 504  Server Errors - Something is wrong on Talkable’s end
+  =================== ======================================================
 
 .. _HTTP Basic Auth: https://en.wikipedia.org/wiki/Basic_access_authentication
 
@@ -145,8 +145,8 @@ Rate limits are not published because the computation logic is evolving
 continuously to maximize reliability and performance for customers.
 
 .. note::
-   In case the request was throttled and the server responded with HTTP status
-   code ``429``, we recommend to retry the request. Consecutive calls might
-   return ``429`` until the load on the server goes down. Your application 
-   should implement a retry logic with incremental backoff in the realm of 
-   seconds and up to minutes.
+  In case the request was throttled and the server responded with HTTP status
+  code ``429``, we recommend to retry the request. Consecutive calls might
+  return ``429`` until the load on the server goes down. Your application
+  should implement a retry logic with incremental backoff in the realm of
+  seconds and up to minutes.
diff --git a/source/api_v2/origins.rst b/source/api_v2/origins.rst
index 99c2079db..803b47562 100644
--- a/source/api_v2/origins.rst
+++ b/source/api_v2/origins.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The Talkable Origins API allows the registration of “off-site” or “backend” purchases, or CRM events. That means they can be used in the referral flow.
+  :description: The Talkable Origins API allows the registration of “off-site” or “backend” purchases, or CRM events. That means they can be used in the referral flow.
 
 Origins
 =======
@@ -14,15 +14,15 @@ off-site transactions, or other off-site events.
 
 .. note::
 
-   The :ref:`standard front-end <integration/custom/overview>` Talkable
-   integration will capture all one-time purchases happening on the client
-   e-commerce site, but will not on its own capture purchases or CRM events
-   happening on the backend. To do this, the |api_v2_origins| must be utilized to
-   feed ‘off-site’ or ‘backend’ purchases or CRM events to Talkable.
+  The :ref:`standard front-end <integration/custom/overview>` Talkable
+  integration will capture all one-time purchases happening on the client
+  e-commerce site, but will not on its own capture purchases or CRM events
+  happening on the backend. To do this, the |api_v2_origins| must be utilized to
+  feed ‘off-site’ or ‘backend’ purchases or CRM events to Talkable.
 
 .. raw:: html
 
-   <h2>Example use cases for the Origins API</h2>
+  <h2>Example use cases for the Origins API</h2>
 
 **Subscription:**
 
diff --git a/source/api_v2/referrals.rst b/source/api_v2/referrals.rst
index 90e7c8ce6..4e4595b8e 100644
--- a/source/api_v2/referrals.rst
+++ b/source/api_v2/referrals.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The Talkable Referrals API allows referrals to be approved or to be voided.
+  :description: The Talkable Referrals API allows referrals to be approved or to be voided.
 
 Referrals
 =========
@@ -11,7 +11,7 @@ The Talkable |api_v2_referrals| allows referrals to be approved or voided.
 
 .. raw:: html
 
-   <h2>Example use cases for the Referrals API</h2>
+  <h2>Example use cases for the Referrals API</h2>
 
 **Voiding referrals after a purchase is returned or canceled:**
 
@@ -30,16 +30,16 @@ The Talkable |api_v2_referrals| allows referrals to be approved or voided.
 
 .. note::
 
-   There is no need to filter the orders for which the Talkable |api_v2_referrals| is
-   called. Call Talkable’s |api_v2_referrals| for all purchases, not just those
-   associated with a referral purchase. Talkable will decide which order numbers
-   are tied to referrals.
-
-   Also: Inside ‘Fraud Settings’ exists two options for Referrals Approval
-   configuration. When ‘Automatic’ Referrals Approvals selected, eligible
-   Referrals will be approved a fixed number of hours or days (per configuration)
-   after the |friend| Purchase and/or Conversion Event. When ‘Manual’ Referrals
-   Approval is selected, referral rewards will only be paid out after either the
-   Talkable |api_v2_referrals| is called with ``{"status": "approved"}`` or after an
-   Admin has approved the referral from inside the Talkable Customer Service
-   Portal.
+  There is no need to filter the orders for which the Talkable |api_v2_referrals| is
+  called. Call Talkable’s |api_v2_referrals| for all purchases, not just those
+  associated with a referral purchase. Talkable will decide which order numbers
+  are tied to referrals.
+
+  Also: Inside ‘Fraud Settings’ exists two options for Referrals Approval
+  configuration. When ‘Automatic’ Referrals Approvals selected, eligible
+  Referrals will be approved a fixed number of hours or days (per configuration)
+  after the |friend| Purchase and/or Conversion Event. When ‘Manual’ Referrals
+  Approval is selected, referral rewards will only be paid out after either the
+  Talkable |api_v2_referrals| is called with ``{"status": "approved"}`` or after an
+  Admin has approved the referral from inside the Talkable Customer Service
+  Portal.
diff --git a/source/campaigns.rst b/source/campaigns.rst
index 980d8a001..f3134ff98 100644
--- a/source/campaigns.rst
+++ b/source/campaigns.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable Campaign is based on interaction between Advocate and Friend. Each step of this interaction has its own View so developer can easily change every single step and customize its appearance and functionality.
+  :description: Talkable Campaign is based on interaction between Advocate and Friend. Each step of this interaction has its own View so developer can easily change every single step and customize its appearance and functionality.
 
 Talkable Campaigns
 ##################
diff --git a/source/campaigns/campaign_placements.rst b/source/campaigns/campaign_placements.rst
index 9ef53d03e..b0e1483a3 100644
--- a/source/campaigns/campaign_placements.rst
+++ b/source/campaigns/campaign_placements.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Campaign Placements let you find the best place for your campaign, so your customers will never miss it.
+  :description: Campaign Placements let you find the best place for your campaign, so your customers will never miss it.
 
 Campaign Placements
 ===================
diff --git a/source/campaigns/campaign_placements/claim_by_name.rst b/source/campaigns/campaign_placements/claim_by_name.rst
index e0e9223ea..499995df0 100644
--- a/source/campaigns/campaign_placements/claim_by_name.rst
+++ b/source/campaigns/campaign_placements/claim_by_name.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Claim by Name campaign appears from the corner of a page showing call-to-action messages to your customers. And it all happens smoothly.
+  :description: Claim by Name campaign appears from the corner of a page showing call-to-action messages to your customers. And it all happens smoothly.
 
 Claim by Name Placement
 =======================
diff --git a/source/campaigns/campaign_placements/floating_widget.rst b/source/campaigns/campaign_placements/floating_widget.rst
index 6048569e1..e0042c580 100644
--- a/source/campaigns/campaign_placements/floating_widget.rst
+++ b/source/campaigns/campaign_placements/floating_widget.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Floating Widget appears from the corner of each page showing call-to-action messages to your customers. And it all happens smoothly.
+  :description: Floating Widget appears from the corner of each page showing call-to-action messages to your customers. And it all happens smoothly.
 
 Floating Widget Placement
 =========================
diff --git a/source/campaigns/campaign_placements/gleam.rst b/source/campaigns/campaign_placements/gleam.rst
index dd3de7760..8623e1446 100644
--- a/source/campaigns/campaign_placements/gleam.rst
+++ b/source/campaigns/campaign_placements/gleam.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Gleam Placement is a special Placement for Reward Gleam type of Campaign.
+  :description: Gleam Placement is a special Placement for Reward Gleam type of Campaign.
 
 Gleam Placement
 ===============
diff --git a/source/campaigns/campaign_placements/loyalty_dashboard.rst b/source/campaigns/campaign_placements/loyalty_dashboard.rst
index 3a4a241ae..9c6877058 100644
--- a/source/campaigns/campaign_placements/loyalty_dashboard.rst
+++ b/source/campaigns/campaign_placements/loyalty_dashboard.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Loyalty Dashboard Placement is a Placement for Loyalty Campaigns.
+  :description: Loyalty Dashboard Placement is a Placement for Loyalty Campaigns.
 
 Loyalty Dashboard Placement
 ===========================
@@ -10,7 +10,7 @@ Loyalty Dashboard Placement
 You can create Loyalty Campaigns and place them on a standalone page on your site. With the Loyalty Dashboard Placement your Campaign will show up on any particular page of your site following rules specified in the placement.
 
 .. note::
-   Customers need to be authenticated in order to view their Loyalty Dashboard. This means that `email` has to be present in the `authenticate_customer` call of the :ref:`Talkable Initialization Script <integration/loyalty/integration_components/initialization_script>`.
+  Customers need to be authenticated in order to view their Loyalty Dashboard. This means that `email` has to be present in the `authenticate_customer` call of the :ref:`Talkable Initialization Script <integration/loyalty/integration_components/initialization_script>`.
 
 It is a good practice to use `https://[your-site]/loyalty` URL for this new page and add a link accessible from any page that makes sense considering your website configuration. Most common uses are links in the user accounts section, or from the user accounts menu.
 
diff --git a/source/campaigns/campaign_placements/loyalty_widget.rst b/source/campaigns/campaign_placements/loyalty_widget.rst
index 422813280..5efe5f4d7 100644
--- a/source/campaigns/campaign_placements/loyalty_widget.rst
+++ b/source/campaigns/campaign_placements/loyalty_widget.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Loyalty Widget Placement is a Placement for Loyalty Campaigns.
+  :description: Loyalty Widget Placement is a Placement for Loyalty Campaigns.
 
 Loyalty Widget Placement
 ========================
@@ -10,7 +10,7 @@ Loyalty Widget Placement
 Once you have your Loyalty Campaigns set up, you can use this placement to show to your customers a widget that will allow them to convert their points into a coupon that can be used on a checkout page.
 
 .. note::
-   If a customer is not signed in (`email` was not provided to the `authenticate_customer` call), the widget prompts them to join the loyalty program and provide the email manually.
+  If a customer is not signed in (`email` was not provided to the `authenticate_customer` call), the widget prompts them to join the loyalty program and provide the email manually.
 
 It is a good practice to show this widget when your customers are about to check out so that they are able to convert their points to a coupon and apply it to the purchase.
 
diff --git a/source/campaigns/campaign_placements/post_purchase.rst b/source/campaigns/campaign_placements/post_purchase.rst
index fa9d4b347..4efdbe57e 100644
--- a/source/campaigns/campaign_placements/post_purchase.rst
+++ b/source/campaigns/campaign_placements/post_purchase.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: With the Post Purchase placement, your Campaign will show up automatically as a popup once the customer made a successful purchase on your site.
+  :description: With the Post Purchase placement, your Campaign will show up automatically as a popup once the customer made a successful purchase on your site.
 
 Post Purchase Placement
 =======================
@@ -17,8 +17,8 @@ Flow
 ----
 
 .. image:: /_static/img/campaign_placements/pp.png
-   :alt: Talkable campaign flow — Post Purchase placement
-   :class: is-minimal
+  :alt: Talkable campaign flow — Post Purchase placement
+  :class: is-minimal
 
 Integration instructions
 ------------------------
diff --git a/source/campaigns/campaign_placements/standalone.rst b/source/campaigns/campaign_placements/standalone.rst
index aea3a7eaf..30df0eda1 100644
--- a/source/campaigns/campaign_placements/standalone.rst
+++ b/source/campaigns/campaign_placements/standalone.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: With the Standalone placement your Campaign will be live on any particular page of your site.
+  :description: With the Standalone placement your Campaign will be live on any particular page of your site.
 
 Standalone Placement
 ====================
@@ -20,8 +20,8 @@ Flow
 ----
 
 .. image:: /_static/img/campaign_placements/standalone.png
-   :alt: Talkable campaign flow — Standalone placement
-   :class: is-minimal
+  :alt: Talkable campaign flow — Standalone placement
+  :class: is-minimal
 
 Integration instructions
 ------------------------
diff --git a/source/campaigns/campaign_types.rst b/source/campaigns/campaign_types.rst
index a6d233e97..ab9e5492e 100644
--- a/source/campaigns/campaign_types.rst
+++ b/source/campaigns/campaign_types.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Motivate customers to share your products with their Friends from anywhere on your site.
+  :description: Motivate customers to share your products with their Friends from anywhere on your site.
 
 Campaign Types
 ==============
@@ -17,8 +17,8 @@ on your site. Invite campaigns are both powerful and versatile. Multiple Invite
 campaigns can be run simultaneously for maximum results.
 
 .. image:: /_static/img/campaign_types/invite.png
-   :alt: Campaign Type - Invite
-   :class: is-minimal
+  :alt: Campaign Type - Invite
+  :class: is-minimal
 
 Advocate Dashboard
 ------------------
@@ -29,8 +29,8 @@ motivated to share. Advocate Dashboards also reduce Customer Service inquiries
 as customers can see statuses directly from the dashboard.
 
 .. image:: /_static/img/campaign_types/dashboard-type.png
-   :alt: Campaign Type - Dashboard
-   :class: is-minimal
+  :alt: Campaign Type - Dashboard
+  :class: is-minimal
 
 Reward Gleam
 ------------
@@ -41,8 +41,8 @@ receives a reward and visits your website the coupon code is captured. The code
 will be highlighted in the Reward Gleam at the bottom of the page.
 
 .. image:: /_static/img/campaign_types/gleam.jpg
-   :alt: Campaign Type - Reward Gleam
-   :class: is-minimal
+  :alt: Campaign Type - Reward Gleam
+  :class: is-minimal
 
 Leaderboard
 -----------
@@ -52,8 +52,8 @@ Leaderboard page based on the number of successful referrals. After an allotted
 time period, top performers can be identified and rewarded with a grand prize.
 
 .. image:: /_static/img/campaign_types/leaderboard.png
-   :alt: Campaign Type - Leaderboard
-   :class: is-minimal
+  :alt: Campaign Type - Leaderboard
+  :class: is-minimal
 
 Tiered Rewards
 --------------
@@ -63,8 +63,8 @@ as they are rewarded for subsequent successful referrals. By setting reward
 goals for Advocates, they are more likely to increase their share rate.
 
 .. image:: /_static/img/campaign_types/tiered_rewards.png
-   :alt: Campaign Type - Tiered Rewards
-   :class: is-minimal
+  :alt: Campaign Type - Tiered Rewards
+  :class: is-minimal
 
 .. _campaigns/claim_by_name:
 
@@ -78,10 +78,10 @@ The Advocate can share their name and describe the referral offer via any channe
 and the Friend can then claim the reward by entering the Advocate's personal name in the Claim by Name popup.
 
 .. note::
-   Claim by Name campaign does not offer any incentives on its own. Both the Advocate and the Friend rewards
-   should be specified in the name sharing campaign (i.e. the campaign with personal name sharing channel enabled).
-   Similarly, the funnel metrics are also tracked within the Advocate campaign.
+  Claim by Name campaign does not offer any incentives on its own. Both the Advocate and the Friend rewards
+  should be specified in the name sharing campaign (i.e. the campaign with personal name sharing channel enabled).
+  Similarly, the funnel metrics are also tracked within the Advocate campaign.
 
 .. image:: /_static/img/campaign_types/claim_by_name.png
-   :alt: Campaign Type - Claim by Name
-   :class: is-minimal
+  :alt: Campaign Type - Claim by Name
+  :class: is-minimal
diff --git a/source/campaigns/designer.rst b/source/campaigns/designer.rst
index a1c729e57..dceadae8c 100644
--- a/source/campaigns/designer.rst
+++ b/source/campaigns/designer.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: That’s where the beauty of your referral campaign is.
+  :description: That’s where the beauty of your referral campaign is.
 
 Designer
 ========
@@ -13,7 +13,7 @@ Web view size
 Canvas size should be equal to a main container width of your site:
 
 .. image:: /_static/img/liquid/designer/image1.png
-   :alt: Page canvas size
+  :alt: Page canvas size
 
 For mobile screens most common width is 320px, but we also support fluid
 width with possibility to set it to 100% to support mobile devices and
@@ -26,7 +26,7 @@ cause it integrates right to the checkout page after user makes a
 purchase (most common size is 800x500px):
 
 .. image:: /_static/img/liquid/designer/image2.png
-   :alt: Advocate Signup/Share Page like a modal
+  :alt: Advocate Signup/Share Page like a modal
 
 .. note:: Overlay cannot be customized.
 
@@ -35,7 +35,7 @@ entirely. Commonly this view looks like a modal window with customer
 site loaded on the back:
 
 .. image:: /_static/img/liquid/designer/image3.png
-   :alt: Friend Claim Page
+  :alt: Friend Claim Page
 
 Most common modal size is 800x500px.
 
@@ -47,7 +47,7 @@ Email size
 Ideally email width is 480px for content:
 
 .. image:: /_static/img/liquid/designer/email-width.png
-   :alt: Email size
+  :alt: Email size
 
 Fonts
 -----
@@ -62,7 +62,7 @@ Also, for emails copy should be placed always on top of solid background
 color, not image:
 
 .. image:: /_static/img/liquid/designer/image5.png
-   :alt: Solid color VS image
+  :alt: Solid color VS image
 
 There are many options for embedding custom fonts, here are most popular
 and solid ones:
@@ -70,7 +70,7 @@ and solid ones:
 1. Purchase web-compatible font on https://www.myfonts.com
 
 .. image:: /_static/img/liquid/designer/image6.png
-   :alt: myfonts.com
+  :alt: myfonts.com
 
 2. Purchase on https://fonts.adobe.com
 
diff --git a/source/campaigns/editor.rst b/source/campaigns/editor.rst
index 9b7a96f47..adc6d73a2 100644
--- a/source/campaigns/editor.rst
+++ b/source/campaigns/editor.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable Campaign Editor allows developers to edit a referral campaign up to their liking and business goals.
+  :description: Talkable Campaign Editor allows developers to edit a referral campaign up to their liking and business goals.
 
 .. _editor:
 
@@ -25,15 +25,15 @@ developers:
 |br|
 
 .. image:: /_static/img/editor/editor.png
-   :alt: Campaign Editor
+  :alt: Campaign Editor
 
 .. container:: hidden
 
   .. toctree::
 
-     editor/variables
-     editor/files
-     editor/history
-     editor/filters
-     editor/videos
-     editor/partials
+    editor/variables
+    editor/files
+    editor/history
+    editor/filters
+    editor/videos
+    editor/partials
diff --git a/source/campaigns/editor/files.rst b/source/campaigns/editor/files.rst
index e6d1f0b67..6d9a0e018 100644
--- a/source/campaigns/editor/files.rst
+++ b/source/campaigns/editor/files.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The Files lets you upload static assets such as images, fonts, and everything else you need to enhance your referral campaign.
+  :description: The Files lets you upload static assets such as images, fonts, and everything else you need to enhance your referral campaign.
 
 Files
 -----
@@ -14,54 +14,53 @@ Used for uploading static assets like images, fonts, etc for campaign purposes.
 1. To upload a file open ``Files``:
 
    .. image:: /_static/img/editor/files-menu-item.png
-      :alt: File uploader menu item
+     :alt: File uploader menu item
 
    |br|
 
 2. Hit ``Choose Files`` button or drag a file(s) to it:
 
    .. image:: /_static/img/editor/files-dragging-files.png
-      :alt: File uploader: dragging files
+     :alt: File uploader: dragging files
 
    |br|
 
 3. Hit ``Upload`` button:
 
    .. image:: /_static/img/editor/files-upload-button.png
-      :alt: File Uploader: upload button
+     :alt: File Uploader: upload button
 
    |br|
 
 4. Uploaded files take place below Upload Bar:
 
    .. image:: /_static/img/editor/files-uploaded.png
-      :alt: File Uploader: files uploaded
+     :alt: File Uploader: files uploaded
 
    |br|
 
 5. Copy Liquid Output Markup by clicking on the file:
 
    .. image:: /_static/img/editor/files-file-output-markup.png
-      :alt: File Uploader: files uploaded
+     :alt: File Uploader: files uploaded
 
    |br|
 
 6. Now paste Output Markup where needed:
 
    .. image:: /_static/img/editor/files-pasting-output-markup.png
-      :alt: File Uploader: pasting output markup
+     :alt: File Uploader: pasting output markup
 
    |br|
 
 7. To preview the file click here:
 
    .. image:: /_static/img/editor/files-preview.png
-      :alt: File Uploader: file preview
+     :alt: File Uploader: file preview
 
    |br|
 
 8. To delete the file click here:
 
    .. image:: /_static/img/editor/files-delete.png
-      :alt: File Uploader: deleting the file
-
+     :alt: File Uploader: deleting the file
diff --git a/source/campaigns/editor/filters.rst b/source/campaigns/editor/filters.rst
index 5c1c63c08..dc468315b 100644
--- a/source/campaigns/editor/filters.rst
+++ b/source/campaigns/editor/filters.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Standard Liquid filters that are available out of box.
+  :description: Standard Liquid filters that are available out of box.
 
 Filters
 -------
@@ -16,18 +16,18 @@ Inserts the font declaration to the page.
 
 .. code-block:: text
 
-   {{ "My Font" | import_font }}
+  {{ "My Font" | import_font }}
 
 Returns:
 
 .. code-block:: css
 
-   @font-face {
-      font-family: 'My Font';
-      src: url('https://d2jjzw81hqbuqv.cloudfront.net/static_assets/files/174201/original/font.woff') format('woff'), url('https://d2jjzw81hqbuqv.cloudfront.net/static_assets/files/174202/original/font.woff2') format('woff2');
-      font-weight: normal;
-      font-style: normal;
-   }
+  @font-face {
+     font-family: 'My Font';
+     src: url('https://d2jjzw81hqbuqv.cloudfront.net/static_assets/files/174201/original/font.woff') format('woff'), url('https://d2jjzw81hqbuqv.cloudfront.net/static_assets/files/174202/original/font.woff2') format('woff2');
+     font-weight: normal;
+     font-style: normal;
+  }
 
 |hr|
 
@@ -38,7 +38,7 @@ Inserts link for an uploaded asset.
 
 .. code-block:: liquid
 
-   {{ "image.jpg" | asset_url }}
+  {{ "image.jpg" | asset_url }}
 
 Example: http://d2jjzw81hqbuqv.cloudfront.net/static_assets/files/745/original/offer-background.jpg
 
@@ -51,7 +51,7 @@ Formats plain text to have HTML formatting. E.g. replace ``\n`` with ``<br/>``.
 
 .. code-block:: text
 
-   {{ "Hello [[advocate_info.email]]\nHere is your reward." | simple_format | interpolate }}
+  {{ "Hello [[advocate_info.email]]\nHere is your reward." | simple_format | interpolate }}
 
 Returns ``Hello John<br/>Here is your reward``.
 
@@ -64,7 +64,7 @@ Encodes a string to be included in a URL.
 
 .. code-block:: text
 
-   http://example.com/?utm_campaign={{ "Campaign Name" | encode_query_argument }}
+  http://example.com/?utm_campaign={{ "Campaign Name" | encode_query_argument }}
 
 Returns ``Campaign%20Name``, so the URL will be
 ``http://example.com/?utm_campaign=Campaign%20Name``.
@@ -78,7 +78,7 @@ Updates query parameters in a URL.
 
 .. code-block:: liquid
 
-   {{ "http://example.com/?a=b&utm_source=foo" | update_query: utm_campaign: "Campaign Name", utm_source: "talkable" }}
+  {{ "http://example.com/?a=b&utm_source=foo" | update_query: utm_campaign: "Campaign Name", utm_source: "talkable" }}
 
 Returns ``http://example.com/?a=b&utm_campaign=Campaign%20Name&utm_source=talkable``.
 
@@ -91,7 +91,7 @@ This filter returns ``true`` or ``false`` for a dataset based on the probability
 
 .. code-block:: liquid
 
-   {{ 50 | probability_by: "param1", "param2", "param3" }}
+  {{ 50 | probability_by: "param1", "param2", "param3" }}
 
 ``50`` returns ``true`` in 50% cases for requested dataset. This filter provides the same result for a particular
 dataset.
@@ -102,23 +102,23 @@ Here is another example that returns ``true`` only in 10% cases for the interpol
 
 .. code-block:: liquid
 
-   {{ 10 | probability_by: advocate_info.email }}
+  {{ 10 | probability_by: advocate_info.email }}
 
 You can ommit passing any parameters and the result will be based on the Advocate offer. Also you may use ``probability`` as an alias which is a little shorter to write:
 
 .. code-block:: liquid
 
-   {{ 50 | probability }}
+  {{ 50 | probability }}
 
 This example can be used in ``Email sending condition`` of Advocate Offer Email template to send email only in 33% cases:
 
 .. code-block:: liquid
 
-   {% assign send_email = 33 | probability %}
+  {% assign send_email = 33 | probability %}
 
-   {% if send_email %}
-     true
-   {% endif %}
+  {% if send_email %}
+    true
+  {% endif %}
 
 |hr|
 
@@ -132,7 +132,7 @@ Simple example:
 
 .. code-block:: liquid
 
-   {{ "100" | rand_by: "param1", "param2" }}
+  {{ "100" | rand_by: "param1", "param2" }}
 
 Always returns ``29``.
 
@@ -140,7 +140,7 @@ Interpolation as a parameter:
 
 .. code-block:: liquid
 
-   {{ "10" | rand_by: advocate_info.email }}
+  {{ "10" | rand_by: advocate_info.email }}
 
 Always returns the same number for a specific email, between 0 and 9.
 
@@ -155,8 +155,8 @@ as an array.
 
 .. code-block:: liquid
 
-   {{ '12345678' | regexp_captures: '(....)(....)' | join: '-' }}
-   {{ 'bogdan@example.com' | regexp_captures: '^([a-z]+)\@([a-z]+)\.([a-z]+)' | json }}
+  {{ '12345678' | regexp_captures: '(....)(....)' | join: '-' }}
+  {{ 'bogdan@example.com' | regexp_captures: '^([a-z]+)\@([a-z]+)\.([a-z]+)' | json }}
 
 |hr|
 
@@ -167,34 +167,34 @@ A/B testing static text:
 
 .. code-block:: liquid
 
-   {{ "ab_test_identifier" | ab_test: "Label 1", "Label 2", "Label N" }}
+  {{ "ab_test_identifier" | ab_test: "Label 1", "Label 2", "Label N" }}
 
 A/B testing text with interpolation:
 
 .. code-block:: liquid
 
-   {{ "share_via_email_subject" | ab_test: "[[site_name]]",
-      "Your friend [[advocate_info.email]] shared this deal with you" | interpolate }}
+  {{ "share_via_email_subject" | ab_test: "[[site_name]]",
+     "Your friend [[advocate_info.email]] shared this deal with you" | interpolate }}
 
 A/B testing an asset:
 
 .. code-block:: liquid
 
-   {{ "offer_background" | ab_test: "background-green.jpg", "background-red.jpg" | asset_url }}
+  {{ "offer_background" | ab_test: "background-green.jpg", "background-red.jpg" | asset_url }}
 
 A/B testing style:
 
 .. code-block:: liquid
 
-   <body style="background-color: {{ 'offer_background' | ab_test: '#d3d3d3', '#ff0000' }}">
-     ...
-   </body>
+  <body style="background-color: {{ 'offer_background' | ab_test: '#d3d3d3', '#ff0000' }}">
+    ...
+  </body>
 
 .. code-block:: liquid
 
-   <h1 style="font-size: {{ 'title_size' | ab_test: '24px', '30px' }}">
-     Sample Title
-   </h1>
+  <h1 style="font-size: {{ 'title_size' | ab_test: '24px', '30px' }}">
+    Sample Title
+  </h1>
 
 |hr|
 
@@ -210,9 +210,9 @@ unless time zone is specified.
 
 .. code-block:: text
 
-   {{ valid_until | date_diff }}
-   {{ valid_until | date_diff: 'Apr 4, 2019' }}
-   {{ '2019-09-01 08:30:00' | date_diff: current_time }}
+  {{ valid_until | date_diff }}
+  {{ valid_until | date_diff: 'Apr 4, 2019' }}
+  {{ '2019-09-01 08:30:00' | date_diff: current_time }}
 
 |hr|
 
@@ -227,8 +227,8 @@ unless time zone is specified.
 
 .. code-block:: liquid
 
-   {{ current_time | date_greater_than: valid_until }}
-   {{ valid_until | date_greater_than: '2019-09-01 08:30:00' }}
+  {{ current_time | date_greater_than: valid_until }}
+  {{ valid_until | date_greater_than: '2019-09-01 08:30:00' }}
 
 |hr|
 
@@ -243,8 +243,8 @@ unless time zone is specified.
 
 .. code-block:: liquid
 
-   {{ current_time | date_greater_than_or_equal: valid_until }}
-   {{ valid_until | date_greater_than_or_equal: '2019-09-01 08:30:00' }}
+  {{ current_time | date_greater_than_or_equal: valid_until }}
+  {{ valid_until | date_greater_than_or_equal: '2019-09-01 08:30:00' }}
 
 |hr|
 
@@ -268,8 +268,8 @@ Available time units (can be used in plural form as well):
 
 .. code-block:: liquid
 
-   {{ valid_until | add_time: 42 }}
-   {{ valid_until | add_time: 3, 'months' }}
+  {{ valid_until | add_time: 42 }}
+  {{ valid_until | add_time: 3, 'months' }}
 
 |hr|
 
@@ -291,11 +291,11 @@ Reference to all available locales can be found in `rails-i18n documentation`_
 
 .. code-block:: liquid
 
-   {{ valid_until | format_date }}
-   {{ valid_until | format_date: format: "%Y-%m-%d" }}
-   {{ valid_until | format_date: locale: "en" }}
-   {{ valid_until | format_date: format: "%Y-%m-%d", locale: "en" }}
-   {{ current_time | format_date }}
+  {{ valid_until | format_date }}
+  {{ valid_until | format_date: format: "%Y-%m-%d" }}
+  {{ valid_until | format_date: locale: "en" }}
+  {{ valid_until | format_date: format: "%Y-%m-%d", locale: "en" }}
+  {{ current_time | format_date }}
 
 |hr|
 
@@ -310,9 +310,9 @@ Reference to all available locales can be found in `rails-i18n documentation`_
 
 .. code-block:: liquid
 
-   {{ valid_until | human_time_ago }}
-   {{ valid_until | human_time_ago: locale: "en" }}
-   {{ current_time | human_time_ago }}
+  {{ valid_until | human_time_ago }}
+  {{ valid_until | human_time_ago: locale: "en" }}
+  {{ current_time | human_time_ago }}
 
 |hr|
 
@@ -325,30 +325,30 @@ Calculate difference between two dates. By default calculates between specified
 
 .. code-block:: text
 
-   {{ "Sun, 02 Jan 2000 10:00:00 PST" | hours_from_time: "Sat, 01 Jan 2000 10:00:00 PST" }}
-   {{ "2015-03-27 17:53" | hours_from_time: "2015-03-27 15:53" }}
+  {{ "Sun, 02 Jan 2000 10:00:00 PST" | hours_from_time: "Sat, 01 Jan 2000 10:00:00 PST" }}
+  {{ "2015-03-27 17:53" | hours_from_time: "2015-03-27 15:53" }}
 
 Next two examples is equivalent.
 
 .. code-block:: liquid
 
-   {{ friend_offer.valid_until | hours_from_time: current_time }}
-   {{ friend_offer.valid_until | hours_from_now }}
+  {{ friend_offer.valid_until | hours_from_time: current_time }}
+  {{ friend_offer.valid_until | hours_from_now }}
 
 Pretty useful example for email sending criteria to prevent sending mail when offer is about to expire.
 
 .. code-block:: liquid
 
-   {% if friend_offer.valid_until %}
-     {% assign difference = friend_offer.valid_until | hours_from_now %}
-     {% if difference > 24 %}
-       true
-     {% else %}
-       false
-     {% endif %}
-   {% else %}
-     true
-   {% endif %}
+  {% if friend_offer.valid_until %}
+    {% assign difference = friend_offer.valid_until | hours_from_now %}
+    {% if difference > 24 %}
+      true
+    {% else %}
+      false
+    {% endif %}
+  {% else %}
+    true
+  {% endif %}
 
 |hr|
 
@@ -359,7 +359,7 @@ Allows inline string interpolation using [[ ]] syntax.
 
 .. code-block:: text
 
-   {{ "Get [[incentives.click.amount | money]] Off" | interpolate }}
+  {{ "Get [[incentives.click.amount | money]] Off" | interpolate }}
 
 |hr|
 
@@ -370,7 +370,7 @@ Calculates the MD5 hash of the string.
 
 .. code-block:: liquid
 
-   {{ "foo" | md5 }}
+  {{ "foo" | md5 }}
 
 Returns ``acbd18db4cc2f85cedef654fccc4a4d8``.
 
@@ -383,7 +383,7 @@ Formats number using current currency.
 
 .. code-block:: liquid
 
-   {{ "50" | money }}
+  {{ "50" | money }}
 
 Returns ``$50.00``.
 
@@ -398,24 +398,24 @@ Available options:
 
 .. container:: ptable
 
-   ============================================================== ==============
-   Example                                                        Result
-   ============================================================== ==============
-   ``{{ "100.11" | money: precision: 0 }}``                       ``$100``
-   ``{{ "100.99" | money: precision: 0 }}``                       ``$101``
-   -------------------------------------------------------------- --------------
-   ``{{ "100.99" | money: strip_insignificant_zeros: true }}``    ``$100.99``
-   ``{{ "100.90" | money: strip_insignificant_zeros: true }}``    ``$100.9``
-   ``{{ "100.00" | money: strip_insignificant_zeros: true }}``    ``$100``
-   -------------------------------------------------------------- --------------
-   ``{{ "100" | money: unit: "€" }}``                             ``€100.00``
-   ``{{ "100" | money: unit: "" }}``                              ``100.00``
-   -------------------------------------------------------------- --------------
-   ``{{ "10049.99" | money: separator: "_" }}``                   ``$10,049_99``
-   ``{{ "10049.99" | money: delimiter: "_" }}``                   ``$10_049.99``
-   -------------------------------------------------------------- --------------
-   ``{{ "100" | money: format: "%n %u", unit: "zł" }}``           ``100.00 zł``
-   ============================================================== ==============
+  ============================================================== ==============
+  Example                                                        Result
+  ============================================================== ==============
+  ``{{ "100.11" | money: precision: 0 }}``                       ``$100``
+  ``{{ "100.99" | money: precision: 0 }}``                       ``$101``
+  -------------------------------------------------------------- --------------
+  ``{{ "100.99" | money: strip_insignificant_zeros: true }}``    ``$100.99``
+  ``{{ "100.90" | money: strip_insignificant_zeros: true }}``    ``$100.9``
+  ``{{ "100.00" | money: strip_insignificant_zeros: true }}``    ``$100``
+  -------------------------------------------------------------- --------------
+  ``{{ "100" | money: unit: "€" }}``                             ``€100.00``
+  ``{{ "100" | money: unit: "" }}``                              ``100.00``
+  -------------------------------------------------------------- --------------
+  ``{{ "10049.99" | money: separator: "_" }}``                   ``$10,049_99``
+  ``{{ "10049.99" | money: delimiter: "_" }}``                   ``$10_049.99``
+  -------------------------------------------------------------- --------------
+  ``{{ "100" | money: format: "%n %u", unit: "zł" }}``           ``100.00 zł``
+  ============================================================== ==============
 
 |hr|
 
@@ -426,7 +426,7 @@ Formats number using conversion rate for loyalty from site settings.
 
 .. code-block:: liquid
 
-   {{ "50" | points }}
+  {{ "50" | points }}
 
 Returns ``500``.
 
@@ -439,19 +439,19 @@ Available options:
 
 .. container:: ptable
 
-   ============================================================== ==============
-   Example                                                        Result
-   ============================================================== ==============
-   ``{{ "10050" | points: delimiter: "_" }}``                     ``100_500``
-   -------------------------------------------------------------- --------------
-   ``{{ "100" | points: format: "%nP" }}``                        ``1000P``
-   -------------------------------------------------------------- --------------
-   ``{{ "100" | points: convert: false }}``                       ``$100.00``
-   ``{{ "1000" | points: convert: false, delimiter: "," }}``      ``$1,000.00``
-   ``{{ "100" | points: convert: false, unit: "€" }}``            ``€100.00``
-   -------------------------------------------------------------- --------------
-   ``{{ "100" | points: percentage_discount: true }}``            ``500``
-   ============================================================== ==============
+  ============================================================== ==============
+  Example                                                        Result
+  ============================================================== ==============
+  ``{{ "10050" | points: delimiter: "_" }}``                     ``100_500``
+  -------------------------------------------------------------- --------------
+  ``{{ "100" | points: format: "%nP" }}``                        ``1000P``
+  -------------------------------------------------------------- --------------
+  ``{{ "100" | points: convert: false }}``                       ``$100.00``
+  ``{{ "1000" | points: convert: false, delimiter: "," }}``      ``$1,000.00``
+  ``{{ "100" | points: convert: false, unit: "€" }}``            ``€100.00``
+  -------------------------------------------------------------- --------------
+  ``{{ "100" | points: percentage_discount: true }}``            ``500``
+  ============================================================== ==============
 
 |hr|
 
@@ -462,7 +462,7 @@ Removes leading and trailing blank symbols from the string.
 
 .. code-block:: text
 
-   {{ "    strip me " | strip }}
+  {{ "    strip me " | strip }}
 
 Returns ``strip me``.
 
@@ -475,7 +475,7 @@ Returns the string, first removing all whitespace on both ends of the string, an
 
 .. code-block:: text
 
-   {{ "   foo   bar        baz " | squish }}
+  {{ "   foo   bar        baz " | squish }}
 
 Returns ``foo bar baz``.
 
@@ -488,7 +488,7 @@ Calculates a tweet length for the string.
 
 .. code-block:: text
 
-   {{ "wow this is a tweet http://example.com" | tweet_length }}
+  {{ "wow this is a tweet http://example.com" | tweet_length }}
 
 Returns ``43``.
 
@@ -501,8 +501,8 @@ Parses the JSON string source into a Liquid data structure.
 
 .. code-block:: liquid
 
-   {% assign var = '{"key": "value"}' | parse_json %}
-   {{ var.key }}
+  {% assign var = '{"key": "value"}' | parse_json %}
+  {{ var.key }}
 
 Returns ``value``.
 
@@ -516,15 +516,15 @@ Accepts singular (required) and plural (optional) forms.
 
 .. container:: ptable
 
-   ============================================================== ==============
-   Example                                                        Result
-   ============================================================== ==============
-   ``{{ 5 | pluralize: "point" }}``                               ``5 points``
-   ``{{ 2 | pluralize: "sheep" }}``                               ``2 sheep``
-   ``{{ 1 | pluralize: "day off" }}``                             ``1 day off``
-   ``{{ 5 | pluralize: "day off" }}``                             ``5 day offs``
-   ``{{ 0 | pluralize: "day off", "days off" }}``                 ``0 days off``
-   ============================================================== ==============
+  ============================================================== ==============
+  Example                                                        Result
+  ============================================================== ==============
+  ``{{ 5 | pluralize: "point" }}``                               ``5 points``
+  ``{{ 2 | pluralize: "sheep" }}``                               ``2 sheep``
+  ``{{ 1 | pluralize: "day off" }}``                             ``1 day off``
+  ``{{ 5 | pluralize: "day off" }}``                             ``5 day offs``
+  ``{{ 0 | pluralize: "day off", "days off" }}``                 ``0 days off``
+  ============================================================== ==============
 
 As shown in the table, simple words can be pluralized without specifying plural form.
 However, more advanced cases require explicit plural form to work correctly.
@@ -538,9 +538,9 @@ Returns channel-specific claim URL.
 
 .. code-block:: liquid
 
-   {{ "facebook" | claim_url }}
-   {{ "linkedin" | claim_url }}
-   {{ "twitter" | claim_url }}
+  {{ "facebook" | claim_url }}
+  {{ "linkedin" | claim_url }}
+  {{ "twitter" | claim_url }}
 
 |hr|
 
@@ -551,7 +551,7 @@ Group an array’s items by a given property.
 
 .. code-block:: liquid
 
-   {{ incentives | group_by: "amount" }}
+  {{ incentives | group_by: "amount" }}
 
 |hr|
 
@@ -562,9 +562,9 @@ Sort an array. Optional arguments for hashes: 1. property name 2. nils order (fi
 
 .. code-block:: liquid
 
-   {{ campaign_tags | sort }}
-   {{ incentives | sort: "amount" }}
-   {{ incentives | sort: "amount", "first" }}
+  {{ campaign_tags | sort }}
+  {{ incentives | sort: "amount" }}
+  {{ incentives | sort: "amount", "first" }}
 
 |hr|
 
@@ -575,7 +575,7 @@ Select all the objects in an array where the key has the given value.
 
 .. code-block:: liquid
 
-   {{ incentives | where: "amount", 10 }}
+  {{ incentives | where: "amount", 10 }}
 
 |hr|
 
@@ -588,16 +588,16 @@ Supports nested interpolation with `[[  ]]`
 
 .. code-block:: liquid
 
-   {{ "welcome_message" | localize }}
-   {{ "offer_title" | localize: "Get [[incentives.referrer.description]]" }}
+  {{ "welcome_message" | localize }}
+  {{ "offer_title" | localize: "Get [[incentives.referrer.description]]" }}
 
 Supports fixed variants for localization, user will be able to set localization value only from this list.
 First value will be a default value, or you can set it using ``default`` option.
 
 .. code-block:: liquid
 
-   {{ "campaign_layout" | localize: "left", "right" }}
-   {{ "header_size" | localize: "h1", "h2", "h3", "h4", default: "h2" }}
+  {{ "campaign_layout" | localize: "left", "right" }}
+  {{ "header_size" | localize: "h1", "h2", "h3", "h4", default: "h2" }}
 
 There is also boolean localization type. It has a strict requirement: exactly two variants which
 determines boolean logics. The first variant is associated with ``true``, the last one — ``false``.
@@ -606,12 +606,12 @@ option (see above for an example). Here is an example of how to use boolean loca
 
 .. code-block:: liquid
 
-   {% assign responsive_font = 'fonts_size' | localize: 'Responsive', 'Fixed', trait: 'boolean' %}
-   {% if responsive_font %}
-     Responsive
-   {% else %}
-     Fixed
-   {% endif %}
+  {% assign responsive_font = 'fonts_size' | localize: 'Responsive', 'Fixed', trait: 'boolean' %}
+  {% if responsive_font %}
+    Responsive
+  {% else %}
+    Fixed
+  {% endif %}
 
 For more information see :ref:`Localization <campaigns/localization>` page.
 
@@ -625,8 +625,8 @@ Available attributes: `red`, `green`, `blue`, `saturation`, `lightness`, `alpha`
 
 .. code-block:: text
 
-   {{ "black" | scale_color: lightness: 50 }}
-   {{ "rgb(256, 128, 0)" | scale_color: saturation: -10 }}
+  {{ "black" | scale_color: lightness: 50 }}
+  {{ "rgb(256, 128, 0)" | scale_color: saturation: -10 }}
 
 |hr|
 
@@ -645,8 +645,8 @@ Returns a new adjusted color based on the following attributes:
 
 .. code-block:: liquid
 
-   {{ "red" | adjust_color: blue: 255 }}
-   {{ "#000000" | adjust_color: alpha: -0.5 }}
+  {{ "red" | adjust_color: blue: 255 }}
+  {{ "#000000" | adjust_color: alpha: -0.5 }}
 
 |hr|
 
@@ -667,16 +667,16 @@ It returns objects with next fields:
 
 .. code-block:: liquid
 
-   {% assign leaders = "3" | leaderboard %}
-   {% for leader in leaders %}
-      <td>{{ leader.leaderboard_rank }}</td>
-      <td>{{ leader.leaderboard_count }}</td>
-   {% endfor %}
+  {% assign leaders = "3" | leaderboard %}
+  {% for leader in leaders %}
+     <td>{{ leader.leaderboard_rank }}</td>
+     <td>{{ leader.leaderboard_count }}</td>
+  {% endfor %}
 
 .. code-block:: liquid
 
-   {% assign leader = "advocate" | leaderboard %}
-   {{ leader.email }} - {{ leader.leaderboard_count }} - {{ leader.leaderboard_rank }}
+  {% assign leader = "advocate" | leaderboard %}
+  {{ leader.email }} - {{ leader.leaderboard_count }} - {{ leader.leaderboard_rank }}
 
 |hr|
 
@@ -702,13 +702,13 @@ Here is how you can embed a screenshot of your website into a campaign view (``s
 
 .. code-block:: liquid
 
-   <img src="{{ site_url | url2png }}" class="campaign-site-on-the-back" />
+  <img src="{{ site_url | url2png }}" class="campaign-site-on-the-back" />
 
 Refresh the screenshot every week:
 
 .. code-block:: liquid
 
-   <img src="{{ 'www.example.com' | url2png: ttl: 604800 }}" />
+  <img src="{{ 'www.example.com' | url2png: ttl: 604800 }}" />
 
 |hr|
 
@@ -720,7 +720,7 @@ This filter strictly follows GS1-128 specification: https://en.wikipedia.org/wik
 
 .. code-block:: liquid
 
-   {% assign barcode = "X" | barcode %}
+  {% assign barcode = "X" | barcode %}
 
 **Here is an example how to convert a coupon code into a barcode:**
 
@@ -728,27 +728,27 @@ HTML:
 
 .. code-block:: liquid
 
-   <table cellspacing="0" cellpadding="0" border="0">
-     {% assign barcode = coupon_code | barcode %}
-       <tr>
-         {% for bar in barcode %}
-           <!-- bar suppose to be true or false -->
-           <td class="barcode-line is-{{ bar }}"></td>
-         {% endfor %}
-       </tr>
-   </table>
+  <table cellspacing="0" cellpadding="0" border="0">
+    {% assign barcode = coupon_code | barcode %}
+      <tr>
+        {% for bar in barcode %}
+          <!-- bar suppose to be true or false -->
+          <td class="barcode-line is-{{ bar }}"></td>
+        {% endfor %}
+      </tr>
+  </table>
 
 SCSS:
 
 .. code-block:: scss
 
-   .barcode-line {
-     height: 50px;
-     width: 2px;
-     &.is-true {
-       background-color: black;
-     }
-   }
+  .barcode-line {
+    height: 50px;
+    width: 2px;
+    &.is-true {
+      background-color: black;
+    }
+  }
 
 .. _Standard liquid filters: https://github.com/Shopify/liquid/wiki/Liquid-for-Designers#standard-filters
 
@@ -768,12 +768,12 @@ The values are in pixels.
 
 .. code-block:: liquid
 
-   {{ coupon.code | barcode_image }}
-   {{ coupon.code | barcode_image: height: 200 }}
-   {{ coupon.code | barcode_image: xdim: 3 }}
-   {{ coupon.code | barcode_image: height: 200, xdim: 3 }}
-   {{ coupon.code | barcode_image: height: 200, xdim: 3, margin: 5 }}
-   {{ coupon.code | barcode_image: height: 200, xdim: 3, margin: 5, bg_transparent: true }}
+  {{ coupon.code | barcode_image }}
+  {{ coupon.code | barcode_image: height: 200 }}
+  {{ coupon.code | barcode_image: xdim: 3 }}
+  {{ coupon.code | barcode_image: height: 200, xdim: 3 }}
+  {{ coupon.code | barcode_image: height: 200, xdim: 3, margin: 5 }}
+  {{ coupon.code | barcode_image: height: 200, xdim: 3, margin: 5, bg_transparent: true }}
 
 Returns a URL string.
 
@@ -786,7 +786,7 @@ Converts given string into a base64 encoded string.
 
 .. code-block:: text
 
-   {{ "some string" | base64_encode }}
+  {{ "some string" | base64_encode }}
 
 Returns ``c29tZSBzdHJpbmc=``
 
@@ -799,7 +799,7 @@ Decodes given base64 encoded string.
 
 .. code-block:: liquid
 
-   {{ "c29tZSBzdHJpbmc=" | base64_decode }}
+  {{ "c29tZSBzdHJpbmc=" | base64_decode }}
 
 Returns ``some string``
 
@@ -814,18 +814,18 @@ Liquid
 
 .. code-block:: liquid
 
-   {% assign my_array = "" | new_array: "element1", "element2" %}
-   {% assign empty_array = "" | new_array %}
+  {% assign my_array = "" | new_array: "element1", "element2" %}
+  {% assign empty_array = "" | new_array %}
 
-   Array: {{ my_array | json }}
-   Empty array: {{ empty_array | json }}
+  Array: {{ my_array | json }}
+  Empty array: {{ empty_array | json }}
 
 Rendered Liquid
 
 .. code-block:: text
 
-   Array: ["element1","element2"]
-   Empty array: []
+  Array: ["element1","element2"]
+  Empty array: []
 
 |hr|
 
@@ -838,16 +838,16 @@ Liquid
 
 .. code-block:: liquid
 
-   {% assign my_array = "" | new_array %}
-   {% assign my_array = my_array | append_to_array: "element1", "element2" %}
+  {% assign my_array = "" | new_array %}
+  {% assign my_array = my_array | append_to_array: "element1", "element2" %}
 
-   Array: {{ my_array | json }}
+  Array: {{ my_array | json }}
 
 Rendered Liquid
 
 .. code-block:: text
 
-   Array: ["element1","element2"]
+  Array: ["element1","element2"]
 
 |hr|
 
@@ -860,18 +860,18 @@ Liquid
 
 .. code-block:: liquid
 
-   {% assign my_hash = "" | new_hash: key: "value", key2: 42 %}
-   {% assign empty_hash = "" | new_hash %}
+  {% assign my_hash = "" | new_hash: key: "value", key2: 42 %}
+  {% assign empty_hash = "" | new_hash %}
 
-   Hash: {{ my_hash | json }}
-   Empty hash: {{ empty_hash | json }}
+  Hash: {{ my_hash | json }}
+  Empty hash: {{ empty_hash | json }}
 
 Rendered Liquid
 
 .. code-block:: text
 
-   Hash: {"key":"value","key2":42}
-   Empty hash: {}
+  Hash: {"key":"value","key2":42}
+  Empty hash: {}
 
 |hr|
 
@@ -884,17 +884,17 @@ Liquid
 
 .. code-block:: liquid
 
-   {% assign my_hash = "" | new_hash: key: "value", key2: 42 %}
-   {% assign my_hash = my_hash | assign_key: "key2", "value2" %}
-   {% assign my_hash = my_hash | assign_key: "key3", "value3" %}
+  {% assign my_hash = "" | new_hash: key: "value", key2: 42 %}
+  {% assign my_hash = my_hash | assign_key: "key2", "value2" %}
+  {% assign my_hash = my_hash | assign_key: "key3", "value3" %}
 
-   Hash: {{ my_hash | json }}
+  Hash: {{ my_hash | json }}
 
 Rendered Liquid
 
 .. code-block:: text
 
-   Hash: {"key":"value","key2":"value2","key3":"value3"}
+  Hash: {"key":"value","key2":"value2","key3":"value3"}
 
 |hr|
 
@@ -905,7 +905,7 @@ Takes a hash and returns the array of its values.
 
 .. code-block:: liquid
 
-   {% assign incentive_configs = incentives | values %}
+  {% assign incentive_configs = incentives | values %}
 
 Returns ``[{ad incentive config}, {fr incentive config}]``
 
@@ -1043,7 +1043,7 @@ Collection of person’s events from the certain date (or for all time when ``fr
 
 .. code-block:: liquid
 
-   {{ "purchase" | events_collection: from_time: "10/14/2018" }}
+  {{ "purchase" | events_collection: from_time: "10/14/2018" }}
 
 Returns
 
@@ -1079,7 +1079,7 @@ Requires Rybbon app to be installed and enabled in order to work.
 
 .. code-block:: liquid
 
-   {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon }}
+  {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon }}
 
 Returns ``https://www.rybbon.net/redeem.php?claimcode=ee645de47765bdbede751c8c6f08a619``
 
@@ -1087,7 +1087,7 @@ Accepts custom amount of reward for Rybbon campaigns with variable denomination.
 
 .. code-block:: liquid
 
-   {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
+  {{ "a9a3472f4ea858758e0cd686de8408e2" | rybbon: amount: 13.5 }}
 
 Find more details about the integration here: :ref:`Rybbon <advanced_features/rybbon>`
 
@@ -1105,7 +1105,7 @@ Implies that there is only one funding source in the Tremendous account.
 
 .. code-block:: liquid
 
-   {{ "DEM8ULSSATK0" | tremendous }}
+  {{ "DEM8ULSSATK0" | tremendous }}
 
 Returns ``https://www.tremendous.com/rewards/payout/reward123``
 
diff --git a/source/campaigns/editor/history.rst b/source/campaigns/editor/history.rst
index 86540016e..639b2b958 100644
--- a/source/campaigns/editor/history.rst
+++ b/source/campaigns/editor/history.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Whenever view or stylesheet is updated, the editor automatically saves changes to History.
+  :description: Whenever view or stylesheet is updated, the editor automatically saves changes to History.
 
 History
 -------
@@ -11,21 +11,21 @@ Whenever view or stylesheet is updated editor saves changes to History which
 you can access from Campaign Editor navigation bar:
 
 .. image:: /_static/img/editor/history-menu-item.png
-   :alt: History: menu item
+  :alt: History: menu item
 
 |br|
 
 1. To preview commit changes click on its link:
 
    .. image:: /_static/img/editor/history-commit-link.png
-      :alt: History: commit preview
+     :alt: History: commit preview
 
    |br|
 
 2. To see commit diff open diff icon (change log will open from the right):
 
    .. image:: /_static/img/editor/history-commit-diff.png
-      :alt: History: commit diff
+     :alt: History: commit diff
 
    |br|
 
diff --git a/source/campaigns/editor/variables.rst b/source/campaigns/editor/variables.rst
index bc73f34a1..2d1974afa 100644
--- a/source/campaigns/editor/variables.rst
+++ b/source/campaigns/editor/variables.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Variables show you dynamic data such as Campaign tag, Advocate info, etc.
+  :description: Variables show you dynamic data such as Campaign tag, Advocate info, etc.
 
 .. _editor_variables:
 
@@ -18,14 +18,14 @@ Each Campaign View has its own set of Variables located inside Editor
 navigation:
 
 .. image:: /_static/img/editor/vars-menu-item.png
-   :alt: Variables: menu item
+  :alt: Variables: menu item
 
 |br|
 
 Each Variable is represented with Name, Liquid notation, Value:
 
 .. image:: /_static/img/editor/vars-variable.png
-   :alt: Variables: variable
+  :alt: Variables: variable
 
 * Name describes meaning of the Variable
 * Notation explains how to write Variable inside Template/Styles editor area
@@ -63,18 +63,18 @@ Personal data for |advocate|.
 
 .. container:: ptable
 
-   ==================== ========================= ==================================================================
-   Property             Value                     Description
-   ==================== ========================= ==================================================================
-   email                "affiliate@example.com"   Advocate email he is registered with
-   first_name           "John"                    Advocate first name provided on Signup
-   last_name            "Smith"                   Advocate last name provided on Signup
-   external_customer_id "1jsh17136"               Advocate unique ID passed by Merchant to :ref:`Talkable Integration
-                                                  <integration/custom/integration_components/initialization_script>` as ``customer_id``
-   sub_choice           false | true              Advocate custom parameter which can be used to pass additional
-                                                  data to Advocate Signup/Share Page
-   purchases_count      0                         Advocate number of tracked store purchases
-   ==================== ========================= ==================================================================
+  ==================== ========================= ==================================================================
+  Property             Value                     Description
+  ==================== ========================= ==================================================================
+  email                "affiliate@example.com"   Advocate email he is registered with
+  first_name           "John"                    Advocate first name provided on Signup
+  last_name            "Smith"                   Advocate last name provided on Signup
+  external_customer_id "1jsh17136"               Advocate unique ID passed by Merchant to :ref:`Talkable Integration
+                                                 <integration/custom/integration_components/initialization_script>` as ``customer_id``
+  sub_choice           false | true              Advocate custom parameter which can be used to pass additional
+                                                 data to Advocate Signup/Share Page
+  purchases_count      0                         Advocate number of tracked store purchases
+  ==================== ========================= ==================================================================
 
 |br|
 
@@ -88,30 +88,30 @@ Personal data for |advocate|.
 
 .. container:: ptable
 
-   ============================== ================================= =============================================================
-   Property                       Value                             Description
-   ============================== ================================= =============================================================
-   id                             1234567890                        Advocate origin id
-   new_customer                   false | true                      Advocate is a new customer or not
-   created_at                     "2016-07-27T00:00:00.000+03:00"   Time when Advocate origin was created
-   event_category                 "purchase"                        Advocate origin event category
-   coupon_codes                   ["AD_DISCOUNT"]                   Coupon codes that are used in Advocate origin
-   ip.address                     "52.6.41.1"                       Advocate IP address
-   ip.qa                          false | true                      Shows if the IP address is listed as QA
-   ip.location.country            "United States"                   Advocate geolocation country based on their IP address
-   ip.location.city               "San Jose"                        Advocate geolocation city based on their IP address
-   ip.location.country_code       "US"                              Advocate geolocation country code based on their IP address
-   ip.location.subdivision_1_code "VA"                              Region-portion of the |iso3166| code for the 1st level region
-                                                                    associated with the IP address
-   ip.location.subdivision_1_code ""                                Region-portion of the |iso3166| code for the 2nd level region
-                                                                    associated with the IP address
-   product.sku                    "AJ7292-002"                      Product SKU
-   product.title                  "Nike Air VaporMax 95"            Product title
-   product.url                    "https://bit.ly/2IPp0rX"          Product URL
-   product.image_url              "https://bit.ly/2GuVAMQ"          Product image URL
-   product.description            "Cool sneakers"                   Product description
-   product.custom_properties      {"price": "190"}                  Product custom properties
-   ============================== ================================= =============================================================
+  ============================== ================================= =============================================================
+  Property                       Value                             Description
+  ============================== ================================= =============================================================
+  id                             1234567890                        Advocate origin id
+  new_customer                   false | true                      Advocate is a new customer or not
+  created_at                     "2016-07-27T00:00:00.000+03:00"   Time when Advocate origin was created
+  event_category                 "purchase"                        Advocate origin event category
+  coupon_codes                   ["AD_DISCOUNT"]                   Coupon codes that are used in Advocate origin
+  ip.address                     "52.6.41.1"                       Advocate IP address
+  ip.qa                          false | true                      Shows if the IP address is listed as QA
+  ip.location.country            "United States"                   Advocate geolocation country based on their IP address
+  ip.location.city               "San Jose"                        Advocate geolocation city based on their IP address
+  ip.location.country_code       "US"                              Advocate geolocation country code based on their IP address
+  ip.location.subdivision_1_code "VA"                              Region-portion of the |iso3166| code for the 1st level region
+                                                                   associated with the IP address
+  ip.location.subdivision_1_code ""                                Region-portion of the |iso3166| code for the 2nd level region
+                                                                   associated with the IP address
+  product.sku                    "AJ7292-002"                      Product SKU
+  product.title                  "Nike Air VaporMax 95"            Product title
+  product.url                    "https://bit.ly/2IPp0rX"          Product URL
+  product.image_url              "https://bit.ly/2GuVAMQ"          Product image URL
+  product.description            "Cool sneakers"                   Product description
+  product.custom_properties      {"price": "190"}                  Product custom properties
+  ============================== ================================= =============================================================
 
 |br|
 
@@ -132,7 +132,7 @@ show it to because it has a scope:
 * for Views which name starts with |friend| it means Friend Coupon Code
 
 .. image:: /_static/img/editor/vars-friend-coupon-code.png
-   :alt: Variables: friend coupon code
+  :alt: Variables: friend coupon code
 
 |br|
 
@@ -143,7 +143,7 @@ Make sure Incentives are correct:
 * If its ``multi-use`` Coupon Code, make sure it has a correct value
 
 .. image:: /_static/img/editor/vars-coupon-list.png
-   :alt: Variables: coupon list
+  :alt: Variables: coupon list
 
 |hr|
 
@@ -161,51 +161,51 @@ Here is an example of ``{{ incentives }}`` Variable with two incentives:
 
 .. code-block:: javascript
 
-   {
-     advocate: {
-       amount: 10.0,
-       description: "$10",
-       percentage: false
-     },
-     friend: {
-       amount: 100.0,
-       description: "100%",
-       percentage: true
-     }
-   }
+  {
+    advocate: {
+      amount: 10.0,
+      description: "$10",
+      percentage: false
+    },
+    friend: {
+      amount: 100.0,
+      description: "100%",
+      percentage: true
+    }
+  }
 
 And here is an example of using ``{{ incentives }}`` values:
 
 .. code-block:: liquid
 
-   Give your friend {{ incentives.friend.description }} OFF!
+  Give your friend {{ incentives.friend.description }} OFF!
 
 Which outputs:
 
 .. code-block:: text
 
-   Give your friend 100% OFF!
+  Give your friend 100% OFF!
 
 .. list-table::
-   :widths: 25 25 50
-   :header-rows: 1
-
-   * - Property
-     - Value
-     - Description
-   * - Liquid slug
-     - "referrer"
-     - Incentive identifier
-   * - amount
-     - 50.0
-     - Incentive amount (float)
-   * - description
-     - "$50"
-     - Formatted Incentive including currency and amount
-   * - percentage
-     - true | false
-     - Type of Incentive amount: fixed or percentage
-   * - required_actions
-     - 0
-     - Number of required actions to trigger reward (i.e. 2 purchases
-       needed to trigger reward)
+  :widths: 25 25 50
+  :header-rows: 1
+
+  * - Property
+    - Value
+    - Description
+  * - Liquid slug
+    - "referrer"
+    - Incentive identifier
+  * - amount
+    - 50.0
+    - Incentive amount (float)
+  * - description
+    - "$50"
+    - Formatted Incentive including currency and amount
+  * - percentage
+    - true | false
+    - Type of Incentive amount: fixed or percentage
+  * - required_actions
+    - 0
+    - Number of required actions to trigger reward (i.e. 2 purchases
+      needed to trigger reward)
diff --git a/source/campaigns/editor/videos.rst b/source/campaigns/editor/videos.rst
index 264ab8d0b..b70ccacd5 100644
--- a/source/campaigns/editor/videos.rst
+++ b/source/campaigns/editor/videos.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: There are videos for you to dive in Liquid. Learn how you can customize screens within Talkable.
+  :description: There are videos for you to dive in Liquid. Learn how you can customize screens within Talkable.
 
 Videos
 ======
@@ -28,22 +28,22 @@ Liquid Tutorial 1: Intro & Navigation
 
 .. raw:: html
 
-   <iframe src="https://fast.wistia.net/embed/iframe/akeaiptdp2" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="363"></iframe>
+  <iframe src="https://fast.wistia.net/embed/iframe/akeaiptdp2" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="363"></iframe>
 
 Liquid Tutorial 2: Using Variables and Filters
 ----------------------------------------------
 
 .. raw:: html
 
-   <iframe src="https://fast.wistia.net/embed/iframe/upf8tdkdy4" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="372"></iframe>
+  <iframe src="https://fast.wistia.net/embed/iframe/upf8tdkdy4" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="372"></iframe>
 
 Liquid Tutorial 3: Using Custom Assets
 --------------------------------------
 
 .. raw:: html
 
-   <iframe src="https://fast.wistia.net/embed/iframe/p08rp1t2gy" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="336"></iframe>
+  <iframe src="https://fast.wistia.net/embed/iframe/p08rp1t2gy" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="640" height="336"></iframe>
 
 .. |liquid_basics| raw:: html
 
-   <a href="https://shopify.dev/api/liquid/basics" target="_blank">https://shopify.dev/api/liquid/basics</a>
+  <a href="https://shopify.dev/api/liquid/basics" target="_blank">https://shopify.dev/api/liquid/basics</a>
diff --git a/source/campaigns/localization.rst b/source/campaigns/localization.rst
index 92f0b0e6a..b4388c24b 100644
--- a/source/campaigns/localization.rst
+++ b/source/campaigns/localization.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can localize your referral campaign. Use the same template with different localization.
+  :description: You can localize your referral campaign. Use the same template with different localization.
 
 Localization
 ############
@@ -14,7 +14,7 @@ Campaign localization is done using a liquid filter `localize`:
 
 .. code-block:: liquid
 
-    {{ "offer_title" | localize: 'Get [[incentives.referrer.description]]' }}
+  {{ "offer_title" | localize: 'Get [[incentives.referrer.description]]' }}
 
 After adding this filter call to the template, go to campaign page and click "Localization" from the navigation menu:
 
@@ -32,4 +32,4 @@ Campaign Localization is copied when campaign is copied, so you are able to use
 
 Campaigns with phone input have country automatically detected based on user IP:
 
-.. image:: /_static/img/phone-input.png
\ No newline at end of file
+.. image:: /_static/img/phone-input.png
diff --git a/source/campaigns/offers_expiration.rst b/source/campaigns/offers_expiration.rst
index 405bc96c8..ee6620a5d 100644
--- a/source/campaigns/offers_expiration.rst
+++ b/source/campaigns/offers_expiration.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can enhance your referral campaign performance by setting up the expiry date for the offer.
+  :description: You can enhance your referral campaign performance by setting up the expiry date for the offer.
 
 Offers Expiration
 #################
@@ -12,7 +12,7 @@ by specifying specific date or setting offer duration in hours.
 
 .. raw:: html
 
-   <h2>Advocate</h2>
+  <h2>Advocate</h2>
 
 - ``Advocate deadline`` - |advocate| will no longer be able to share after this date.
 - All existing |Advocate| offers are always affected if specified date is changed
@@ -25,7 +25,7 @@ by specifying specific date or setting offer duration in hours.
 
 .. raw:: html
 
-   <h2>Friend</h2>
+  <h2>Friend</h2>
 
 - ``Friend Deadline`` - |Friend| will no longer be able to claim the offer after this date.
 - ``Friend Offer Duration`` - |Friend| will no longer be able to claim the offer X
diff --git a/source/campaigns/tutorials.rst b/source/campaigns/tutorials.rst
index d4a6362ff..f15417360 100644
--- a/source/campaigns/tutorials.rst
+++ b/source/campaigns/tutorials.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This tutorial will show you how to create, launch, and track your referral program.
+  :description: This tutorial will show you how to create, launch, and track your referral program.
 
 Tutorials
 =========
@@ -11,7 +11,7 @@ Contents:
 
 .. toctree::
 
-   tutorials/global
-   tutorials/offers_show
-   tutorials/offers_claim
-   tutorials/incentive_criteria
+  tutorials/global
+  tutorials/offers_show
+  tutorials/offers_claim
+  tutorials/incentive_criteria
diff --git a/source/campaigns/tutorials/global.rst b/source/campaigns/tutorials/global.rst
index 4601dc1ff..2d1ff3060 100644
--- a/source/campaigns/tutorials/global.rst
+++ b/source/campaigns/tutorials/global.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Learn how to work with multiple ZeroClipboard instances.
+  :description: Learn how to work with multiple ZeroClipboard instances.
 
 Global
 ------
diff --git a/source/campaigns/tutorials/incentive_criteria.rst b/source/campaigns/tutorials/incentive_criteria.rst
index 6d763a935..bd8406cff 100644
--- a/source/campaigns/tutorials/incentive_criteria.rst
+++ b/source/campaigns/tutorials/incentive_criteria.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: When you create an incentive for Advocate or Friend, you can set terms and conditions.
+  :description: When you create an incentive for Advocate or Friend, you can set terms and conditions.
 
 .. _incentive_criteria:
 
@@ -18,13 +18,13 @@ If condition is left blank, it is assumed to be ``true``.
 
 .. raw:: html
 
-   <h4>Example</h4>
+  <h4>Example</h4>
 
 If you want to reward |advocate| only if |friend| is a new customer and used |br|
 Talkable single-use coupon at checkout, the right trigger condition would be:
 
 .. image:: /_static/img/incentive-criteria-1.png
-   :alt: Incentive Trigger Criteria
+  :alt: Incentive Trigger Criteria
 
 If condition evaluates to anything else than ``true`` or ``false``, the value
 it returns will be visible in Referrals Report.
@@ -33,7 +33,7 @@ This way, you can know which part of a condition was the reason |advocate| didn
 get a reward:
 
 .. image:: /_static/img/incentive-criteria-2.png
-   :alt: Incentive Trigger Criteria
+  :alt: Incentive Trigger Criteria
 
 .. image:: /_static/img/incentive-criteria-3.png
-   :alt: Referrals Report
+  :alt: Referrals Report
diff --git a/source/campaigns/tutorials/offers_claim.rst b/source/campaigns/tutorials/offers_claim.rst
index d6550d991..6b18719cc 100644
--- a/source/campaigns/tutorials/offers_claim.rst
+++ b/source/campaigns/tutorials/offers_claim.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Email gating lets you get a referred Friend’s email — just ask for it in exchange for a reward.
+  :description: Email gating lets you get a referred Friend’s email — just ask for it in exchange for a reward.
 
 Friend Claim Page
 -----------------
@@ -19,7 +19,7 @@ field, submit button, and "signup for latest news" checkbox.
 First of all, turn on email gating in Restricted settings:
 
 .. image:: /_static/img/liquid/gating/image1.png
-   :alt:
+  :alt:
 
 **Basic Setup**
 
diff --git a/source/campaigns/tutorials/offers_show.rst b/source/campaigns/tutorials/offers_show.rst
index 35d20c217..e77bfd538 100644
--- a/source/campaigns/tutorials/offers_show.rst
+++ b/source/campaigns/tutorials/offers_show.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Instant reward campaign lets you reward your brand Advocate immediately — right after a referral link to a Friend was sent.
+  :description: Instant reward campaign lets you reward your brand Advocate immediately — right after a referral link to a Friend was sent.
 
 Advocate Signup/Share Page
 --------------------------
diff --git a/source/campaigns/views.rst b/source/campaigns/views.rst
index 28ee4721e..08ed5cc6f 100644
--- a/source/campaigns/views.rst
+++ b/source/campaigns/views.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Two powerful instruments, Page-Views and Email-Views, let you control nearly every step of the refer-a-friend campaign. You won’t miss the moment of your success.
+  :description: Two powerful instruments, Page-Views and Email-Views, let you control nearly every step of the refer-a-friend campaign. You won’t miss the moment of your success.
 
 Views
 =====
@@ -12,7 +12,7 @@ step of the refer-a-friend campaign. Such page or email is called a View. You ca
 control appearance of each View by visiting Appearance:
 
 .. image:: /_static/img/campaign/subnav.png
-   :alt: Campaign Appearance
+  :alt: Campaign Appearance
 
 |br|
 |br|
@@ -47,11 +47,11 @@ After pre-validation Talkable campaign level validation kicks in:
 
 .. toctree::
 
-   views/offers_show
-   views/notifier_offers_email
-   views/notifier_offers_share_via_email
-   views/notifier_offers_share_via_email_reminder
-   views/offers_claim
-   views/advocate_rewards_confirmation
-   views/advocate_rewards_paid
-   views/friend_rewards_paid
+  views/offers_show
+  views/notifier_offers_email
+  views/notifier_offers_share_via_email
+  views/notifier_offers_share_via_email_reminder
+  views/offers_claim
+  views/advocate_rewards_confirmation
+  views/advocate_rewards_paid
+  views/friend_rewards_paid
diff --git a/source/campaigns/views/advocate_rewards_confirmation.rst b/source/campaigns/views/advocate_rewards_confirmation.rst
index 3613d8278..e2ae94eff 100644
--- a/source/campaigns/views/advocate_rewards_confirmation.rst
+++ b/source/campaigns/views/advocate_rewards_confirmation.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Want to know if your brand Advocate likes your reward? Send them a confirmation email — and get to know if it’s yes or no.
+  :description: Want to know if your brand Advocate likes your reward? Send them a confirmation email — and get to know if it’s yes or no.
 
 .. _advocate_rewards_confirmation:
 
@@ -13,7 +13,7 @@ Main purpose of this email is to send a notification about Reward via email to a
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default is sent immediately after the reward is created, but can be delayed by configuration.
 However, this email does not work with tiered campaigns because rewards are being issued after the referral approval.
diff --git a/source/campaigns/views/advocate_rewards_paid.rst b/source/campaigns/views/advocate_rewards_paid.rst
index 463b09bad..aa47cc39e 100644
--- a/source/campaigns/views/advocate_rewards_paid.rst
+++ b/source/campaigns/views/advocate_rewards_paid.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Send email to your brand Advocate when their account has been credited or a partial refund has been issued.
+  :description: Send email to your brand Advocate when their account has been credited or a partial refund has been issued.
 
 Advocate Reward Paid Email
 --------------------------
@@ -19,15 +19,15 @@ Frequently used Variables:
 - Main |cta| should point to a merchant site to start shopping ``{{ proceed_to_advocate_destination_url }}``.
 
 .. image:: /_static/img/basics/advocate-reward-paid-email-v2.png
-   :alt: Advocate Reward Paid Email
+  :alt: Advocate Reward Paid Email
 
 .. include:: /partials/developer_email_note.rst
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default is sent immediately after the reward status turns into `Paid`, but can be delayed by configuration. |br|
 
 When the coupon list for Sharing or Signup incentive is empty at the moment of reward issuing, **Reward Paid Email** will not be sent.
-We will try to reward the Advocate and send the email in the background for 60 days (with an increasing duration between retries) in the case of coupon list fulfillment.
\ No newline at end of file
+We will try to reward the Advocate and send the email in the background for 60 days (with an increasing duration between retries) in the case of coupon list fulfillment.
diff --git a/source/campaigns/views/friend_rewards_paid.rst b/source/campaigns/views/friend_rewards_paid.rst
index a6fd4e00c..39d1caa47 100644
--- a/source/campaigns/views/friend_rewards_paid.rst
+++ b/source/campaigns/views/friend_rewards_paid.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: It`s good to give thanks to a Friend. Send a reward via email, and remind them about it later on.
+  :description: It`s good to give thanks to a Friend. Send a reward via email, and remind them about it later on.
 
 .. _friend_rewards_paid:
 
@@ -27,22 +27,22 @@ Frequently used Variables:
 |br|
 
 .. image:: /_static/img/basics/friend-claim-email.png
-   :alt: Friend Claim Email
+  :alt: Friend Claim Email
 
 |br|
 
 .. code-block:: liquid
 
-   Here is your {{ reward.incentive.description }} OFF deal you just claimed!
-   Use it on any purchase by {{ valid_until }}
-   Coupon code: {{ coupon_code }}
-   <a href="{{ proceed_to_merchant_path }}">Shop now</a>
+  Here is your {{ reward.incentive.description }} OFF deal you just claimed!
+  Use it on any purchase by {{ valid_until }}
+  Coupon code: {{ coupon_code }}
+  <a href="{{ proceed_to_merchant_path }}">Shop now</a>
 
 .. include:: /partials/developer_email_note.rst
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default is sent immediately after the reward is created, but can be delayed by configuration.
 
diff --git a/source/campaigns/views/notifier_offers_email.rst b/source/campaigns/views/notifier_offers_email.rst
index a5110a84c..9710305b4 100644
--- a/source/campaigns/views/notifier_offers_email.rst
+++ b/source/campaigns/views/notifier_offers_email.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Send email to tell your Advocate what your referral program is about. Motivate them to share your offer.
+  :description: Send email to tell your Advocate what your referral program is about. Motivate them to share your offer.
 
 Advocate Offer Email
 --------------------
@@ -25,7 +25,7 @@ Main |cta| should point to an Advocate Signup/Share Page — ``{{ share_page_url
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default is sent immediately after the offer is created, but can be delayed by configuration.
 
diff --git a/source/campaigns/views/notifier_offers_share_via_email.rst b/source/campaigns/views/notifier_offers_share_via_email.rst
index 80089e872..82bddbb88 100644
--- a/source/campaigns/views/notifier_offers_share_via_email.rst
+++ b/source/campaigns/views/notifier_offers_share_via_email.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Send an invite email to a Friend showing their special share link. Make the email looks personal — just like it's written for them.
+  :description: Send an invite email to a Friend showing their special share link. Make the email looks personal — just like it's written for them.
 
 .. _friend_share_email_view:
 
@@ -23,13 +23,13 @@ Frequently used Variables:
 |br|
 
 .. image:: /_static/img/basics/friend-share-email.png
-   :alt: Friend Share Email
+  :alt: Friend Share Email
 
 .. include:: /partials/developer_email_note.rst
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default is sent immediately after the offer is shared, but can be delayed by configuration.
 
diff --git a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
index b008c880f..28bbfd889 100644
--- a/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
+++ b/source/campaigns/views/notifier_offers_share_via_email_reminder.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Sometimes you need only one email to remind a Friend about your offer — just check on the checkbox on the Advocate Signup/Share Page.
+  :description: Sometimes you need only one email to remind a Friend about your offer — just check on the checkbox on the Advocate Signup/Share Page.
 
 .. _friend_share_email_reminder_view:
 
@@ -21,13 +21,13 @@ particular email.
 |br|
 
 .. image:: /_static/img/basics/friend-share-email-reminder.png
-   :alt: Friend Share Email Reminder
+  :alt: Friend Share Email Reminder
 
 .. include:: /partials/developer_email_note.rst
 
 .. raw:: html
 
-   <h2>Email sending conditions</h2>
+  <h2>Email sending conditions</h2>
 
 By default the email is sent in 72 hours after the offer is shared.
 
diff --git a/source/campaigns/views/offers_claim.rst b/source/campaigns/views/offers_claim.rst
index c747a6fb7..743fc2c93 100644
--- a/source/campaigns/views/offers_claim.rst
+++ b/source/campaigns/views/offers_claim.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Tell a Friend that every link they share will be rewarded.
+  :description: Tell a Friend that every link they share will be rewarded.
 
 .. _friend_claim_page_view:
 
@@ -25,23 +25,23 @@ Frequently used Variables:
 |br|
 
 .. image:: /_static/img/basics/friend-claim-page.png
-   :alt: Friend Claim Page
+  :alt: Friend Claim Page
 
 .. code-block:: liquid
 
-   {% if offer_active %}
-     Copy your code: {{ coupon_code }}
-     <a href="{{ proceed_to_merchant_path }}">Shop now</a>
-     Offer is valid until {{ friend_offer.valid_until | format_date }}.
-   {% else %}
-     Offer expired.
-     <a href="{{ proceed_to_merchant_path }}">Proceed without offer</a>
-   {% endif %}
+  {% if offer_active %}
+    Copy your code: {{ coupon_code }}
+    <a href="{{ proceed_to_merchant_path }}">Shop now</a>
+    Offer is valid until {{ friend_offer.valid_until | format_date }}.
+  {% else %}
+    Offer expired.
+    <a href="{{ proceed_to_merchant_path }}">Proceed without offer</a>
+  {% endif %}
 
 .. note::
 
-   Do not change ``name`` and ``class`` attributes, otherwise
-   functionality won’t work. `js-` class prefix means it is used in Talkable API.
+  Do not change ``name`` and ``class`` attributes, otherwise
+  functionality won’t work. `js-` class prefix means it is used in Talkable API.
 
 Related tutorials for this View:
 
diff --git a/source/campaigns/views/offers_show.rst b/source/campaigns/views/offers_show.rst
index 6a34c3eb4..83be9e3f1 100644
--- a/source/campaigns/views/offers_show.rst
+++ b/source/campaigns/views/offers_show.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Advocate Signup/Share Page - Combination of Signup and Share forms. Shows the value proposition to Advocate and Friend — they both will receive an exclusive discount.
+  :description: Advocate Signup/Share Page - Combination of Signup and Share forms. Shows the value proposition to Advocate and Friend — they both will receive an exclusive discount.
 
 .. _advocate_signup_share_page_view:
 
@@ -15,12 +15,12 @@ First we show Advocate Signup Form. Signup is skipped when we know the advocate
 On this page Advocate signs up by entering their email address and phone number(optional).
 
 .. image:: /_static/img/basics/advocate-signup-form.png
-   :alt: Advocate Signup Form
+  :alt: Advocate Signup Form
 
 After signup, without reloading page, Advocate Share form is shown:
 
 .. image:: /_static/img/basics/advocate-share-form.png
-   :alt: Advocate Share form
+  :alt: Advocate Share form
 
 Here |advocate| shares an offer with their |friend|\s. Explain the value proposition
 to |advocate| and |friend|, that both will receive an exclusive discount.
@@ -33,49 +33,49 @@ Available sharing methods:
 
 .. raw:: html
 
-   <h4>Email sharing example:</h4>
+  <h4>Email sharing example:</h4>
 
 |br|
 
 .. image:: /_static/img/basics/advocate-share-via-email.png
-   :alt: Advocate Share via Email Form
+  :alt: Advocate Share via Email Form
 
 Note ``Send my friend a reminder e-mail in 3 days`` checkbox — this is :ref:`friend_share_email_reminder_view`
 trigger.
 
 .. raw:: html
 
-   <h4>Facebook sharing example (simplified):</h4>
+  <h4>Facebook sharing example (simplified):</h4>
 
 .. code-block:: html
 
-   <a href="#" class="js-share-offer-via-facebook">
-     Share on Facebook
-   </a>
+  <a href="#" class="js-share-offer-via-facebook">
+    Share on Facebook
+  </a>
 
 .. raw:: html
 
-   <h4>Twitter sharing example (simplified):</h4>
+  <h4>Twitter sharing example (simplified):</h4>
 
 .. code-block:: html
 
-   <a href="{{ twitter_share_link }}">
-     Share on Twitter
-   </a>
+  <a href="{{ twitter_share_link }}">
+    Share on Twitter
+  </a>
 
 .. raw:: html
 
-   <h4>Share by link example (simplified):</h4>
+  <h4>Share by link example (simplified):</h4>
 
 .. code-block:: html
 
-   <div data-clipboard-text="{{ short_url }}"
-        data-copied-label="Copied!"
-        data-placement="top"
-        title="Click to Copy"
-        class="js-share-by-link">
-     Copy and share by link
-   </div>
+  <div data-clipboard-text="{{ short_url }}"
+       data-copied-label="Copied!"
+       data-placement="top"
+       title="Click to Copy"
+       class="js-share-by-link">
+    Copy and share by link
+  </div>
 
 - ``data-clipboard-text`` — data to be copied to a user clipboard on click.
 - ``data-copied-label`` — tooltip text after copying.
@@ -84,8 +84,8 @@ trigger.
 
 .. note::
 
-   Do not change ``name`` and ``class`` attributes, otherwise
-   functionality won’t work. `js-` class prefix means it is used in Talkable API.
+  Do not change ``name`` and ``class`` attributes, otherwise
+  functionality won’t work. `js-` class prefix means it is used in Talkable API.
 
 Related tutorials for this View:
 
diff --git a/source/custom_integration.rst b/source/custom_integration.rst
index 071391b2e..e58db8778 100644
--- a/source/custom_integration.rst
+++ b/source/custom_integration.rst
@@ -8,11 +8,11 @@ Contents:
 
 .. toctree::
 
-   custom_integration/crowdtwist
-   custom_integration/chatgpt
-   custom_integration/validity
-   custom_integration/trustpilot
-   custom_integration/recharge
-   custom_integration/salesforce
-   custom_integration/microsoft
+  custom_integration/crowdtwist
+  custom_integration/chatgpt
+  custom_integration/validity
+  custom_integration/trustpilot
+  custom_integration/recharge
+  custom_integration/salesforce
+  custom_integration/microsoft
 
diff --git a/source/custom_integration/chatgpt.rst b/source/custom_integration/chatgpt.rst
index 78950cd47..c12df0383 100644
--- a/source/custom_integration/chatgpt.rst
+++ b/source/custom_integration/chatgpt.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate ChatGPT with your Talkable system to generate AI-driven text for various use cases like AD notes.
+  :description: Integrate ChatGPT with your Talkable system to generate AI-driven text for various use cases like AD notes.
 
 ChatGPT
 =======
@@ -11,4 +11,4 @@ With this integration, Talkable utilizes OpenAI's ChatGPT API to generate custom
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/custom_integration/crowdtwist.rst b/source/custom_integration/crowdtwist.rst
index e92ae1a69..994695066 100644
--- a/source/custom_integration/crowdtwist.rst
+++ b/source/custom_integration/crowdtwist.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate store credit rewards using CrowdTwist API with Talkable.
+  :description: Integrate store credit rewards using CrowdTwist API with Talkable.
 
 CrowdTwist
 ==========
@@ -11,4 +11,4 @@ With this integration, Talkable enables store credit rewards through the CrowdTw
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/custom_integration/recharge.rst b/source/custom_integration/recharge.rst
index 742f771cf..86c41f8b2 100644
--- a/source/custom_integration/recharge.rst
+++ b/source/custom_integration/recharge.rst
@@ -9,8 +9,8 @@ Recharge
 
 .. note::
 
-   This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor, please
-   contact your Customer Success Manager to apply it to your campaigns.
+  This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor, please
+  contact your Customer Success Manager to apply it to your campaigns.
 
 Recharge allows consumers to apply accumulated rewards towards upcoming subscription orders. Please note this is essentially ‘stacking’ of referral rewards.
 
diff --git a/source/custom_integration/trustpilot.rst b/source/custom_integration/trustpilot.rst
index edb550197..831799af8 100644
--- a/source/custom_integration/trustpilot.rst
+++ b/source/custom_integration/trustpilot.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate Trustpilot with your Talkable system to track reviews as events within campaigns.
+  :description: Integrate Trustpilot with your Talkable system to track reviews as events within campaigns.
 
 Trustpilot
 ==========
@@ -11,4 +11,4 @@ With this integration, Talkable tracks reviews as events in campaigns using Trus
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/custom_integration/validity.rst b/source/custom_integration/validity.rst
index eecc66110..86ad4bf2d 100644
--- a/source/custom_integration/validity.rst
+++ b/source/custom_integration/validity.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Integrate Validity with your Talkable system for additional email validation within campaigns.
+  :description: Integrate Validity with your Talkable system for additional email validation within campaigns.
 
 Validity
 ========
@@ -11,4 +11,4 @@ With this integration, Talkable performs additional validation on email addresse
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation.rst b/source/email_marketing_and_automation.rst
index 0f708c26e..d3269629c 100644
--- a/source/email_marketing_and_automation.rst
+++ b/source/email_marketing_and_automation.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: With these tools, Talkable synchronizes all people who opt-in for Talkable marketing communication during signup. This way you will keep all your emails in one place in an automated way.
+  :description: With these tools, Talkable synchronizes all people who opt-in for Talkable marketing communication during signup. This way you will keep all your emails in one place in an automated way.
 
 Email Marketing & Automation
 ############################
@@ -13,28 +13,28 @@ Contents:
 
 .. toctree::
 
-   email_marketing_and_automation/bluecore
-   email_marketing_and_automation/braze
-   email_marketing_and_automation/cordial
-   email_marketing_and_automation/createsend
-   email_marketing_and_automation/cheetah
-   email_marketing_and_automation/klaviyo
-   email_marketing_and_automation/yotpo
-   email_marketing_and_automation/ometria
-   email_marketing_and_automation/oracle_bronto
-   email_marketing_and_automation/omnisend
-   email_marketing_and_automation/mailchimp
-   email_marketing_and_automation/sailthru
-   email_marketing_and_automation/sendgrid
-   email_marketing_and_automation/sfmc
-   email_marketing_and_automation/getresponse
-   email_marketing_and_automation/targetbay
-   email_marketing_and_automation/emarsys
-   email_marketing_and_automation/exponea
-   email_marketing_and_automation/hubspot
-   email_marketing_and_automation/iterable
-   email_marketing_and_automation/listrak
-   email_marketing_and_automation/attentive
-   email_marketing_and_automation/apsis
-   email_marketing_and_automation/what_counts_pro
-   email_marketing_and_automation/custom_app
+  email_marketing_and_automation/bluecore
+  email_marketing_and_automation/braze
+  email_marketing_and_automation/cordial
+  email_marketing_and_automation/createsend
+  email_marketing_and_automation/cheetah
+  email_marketing_and_automation/klaviyo
+  email_marketing_and_automation/yotpo
+  email_marketing_and_automation/ometria
+  email_marketing_and_automation/oracle_bronto
+  email_marketing_and_automation/omnisend
+  email_marketing_and_automation/mailchimp
+  email_marketing_and_automation/sailthru
+  email_marketing_and_automation/sendgrid
+  email_marketing_and_automation/sfmc
+  email_marketing_and_automation/getresponse
+  email_marketing_and_automation/targetbay
+  email_marketing_and_automation/emarsys
+  email_marketing_and_automation/exponea
+  email_marketing_and_automation/hubspot
+  email_marketing_and_automation/iterable
+  email_marketing_and_automation/listrak
+  email_marketing_and_automation/attentive
+  email_marketing_and_automation/apsis
+  email_marketing_and_automation/what_counts_pro
+  email_marketing_and_automation/custom_app
diff --git a/source/email_marketing_and_automation/apsis.rst b/source/email_marketing_and_automation/apsis.rst
index fc496f7ff..cfb1d3f00 100644
--- a/source/email_marketing_and_automation/apsis.rst
+++ b/source/email_marketing_and_automation/apsis.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with Apsis integration.
+  :description: Synchronize Talkable collected emails with Apsis integration.
 
 Apsis
 =====
@@ -11,4 +11,4 @@ With this integration, Talkable synchronizes all people who opt in for Talkable
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/attentive.rst b/source/email_marketing_and_automation/attentive.rst
index cd77a8862..ce3d1ffcb 100644
--- a/source/email_marketing_and_automation/attentive.rst
+++ b/source/email_marketing_and_automation/attentive.rst
@@ -9,8 +9,8 @@ Attentive
 
 .. code-block:: text
 
-   This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor,
-   please contact your Customer Success Manager to apply it to your campaigns.
+  This is a custom integration that can be implemented with extra effort. If you wish to integrate this vendor,
+  please contact your Customer Success Manager to apply it to your campaigns.
 
 Talkable converts customers into brand advocates by enabling trusted, word-of-mouth referrals. Attentive connects with customers on the most engaging channel: SMS.
 
@@ -21,7 +21,7 @@ Together, Talkable and Attentive drive personalized brand engagement and the **a
 1. Capture phone numbers through Talkable to seamlessly grow your SMS subscriber list. The integration automatically passes these numbers to your Attentive messaging flow.
 
   .. image:: /_static/img/email_marketing_and_automation/signup2.png
-      :alt: Signup
+    :alt: Signup
 
 2. Promote refer-a-friend to your SMS list to facilitate increased sharing. Mobile messages have a 99% open rate.
 
@@ -45,7 +45,7 @@ It supports next data to be synchronized from Talkable to Attentive:
 
 .. note::
 
-    For phone and phone opt-in synchronization, corresponding attributes should be configured in a Talkable campaign: :ref:`Phone number gating <advanced_features/phone_number_gating>`
+  For phone and phone opt-in synchronization, corresponding attributes should be configured in a Talkable campaign: :ref:`Phone number gating <advanced_features/phone_number_gating>`
 
 Here are the conditions when Talkable acquires phone numbers:
 
@@ -80,7 +80,7 @@ Please use the following guide to start using an app you need:
 1. Navigate into the App store:
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_navigation.png
-      :alt: App store navigation
+    :alt: App store navigation
 
 2. Choose an app you need by clicking “Install”
 
@@ -90,7 +90,7 @@ instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/attentive_activate.png
-      :alt: Attentive
+    :alt: Attentive
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/bluecore.rst b/source/email_marketing_and_automation/bluecore.rst
index c9fd7b224..fad6d5234 100644
--- a/source/email_marketing_and_automation/bluecore.rst
+++ b/source/email_marketing_and_automation/bluecore.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to Bluecore for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to Bluecore for email marketing and automation.
 
 Bluecore
 ========
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to Bluecore, facilitating ef
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/braze.rst b/source/email_marketing_and_automation/braze.rst
index 7d057dd62..1986d4c8d 100644
--- a/source/email_marketing_and_automation/braze.rst
+++ b/source/email_marketing_and_automation/braze.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to Braze for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to Braze for email marketing and automation.
 
 Braze
 =====
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to Braze, enabling efficient
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/cheetah.rst b/source/email_marketing_and_automation/cheetah.rst
index d04105c30..cf07852c0 100644
--- a/source/email_marketing_and_automation/cheetah.rst
+++ b/source/email_marketing_and_automation/cheetah.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize emails and customer fields collected with Talkable to Cheetah for email marketing and automation.
+  :description: Synchronize emails and customer fields collected with Talkable to Cheetah for email marketing and automation.
 
 Cheetah
 =======
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins and customer fields to Cheet
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/cordial.rst b/source/email_marketing_and_automation/cordial.rst
index fb0bbd9ac..b96afce1e 100644
--- a/source/email_marketing_and_automation/cordial.rst
+++ b/source/email_marketing_and_automation/cordial.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with Cordial integration.
+  :description: Synchronize Talkable collected emails with Cordial integration.
 
 Cordial
 =======
diff --git a/source/email_marketing_and_automation/createsend.rst b/source/email_marketing_and_automation/createsend.rst
index 8db66dbb7..cbf5d38ad 100644
--- a/source/email_marketing_and_automation/createsend.rst
+++ b/source/email_marketing_and_automation/createsend.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with CreateSend integration.
+  :description: Synchronize Talkable collected emails with CreateSend integration.
 
 CreateSend
 ==========
@@ -11,4 +11,4 @@ With this integration, Talkable synchronizes all people who opt in for Talkable
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/custom_app.rst b/source/email_marketing_and_automation/custom_app.rst
index 3ff558522..3f95d1362 100644
--- a/source/email_marketing_and_automation/custom_app.rst
+++ b/source/email_marketing_and_automation/custom_app.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Custom App allows you to send Talkable data to a desired destination such as your site, ESP, CDP.
+  :description: Custom App allows you to send Talkable data to a desired destination such as your site, ESP, CDP.
 
 Custom App
 ==========
@@ -16,17 +16,17 @@ Set Up
 1. Navigate to the App store:
 
    .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+     :alt: App store step 1
 
    .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+     :alt: App store step 2
 
 2. Choose a `Custom app` and click “Install”
 3. Fill in `Endpoint URL` and `App name` fields, and enable the required actions.
 4. Complete installation and enable the app:
 
    .. image:: /_static/img/email_marketing_and_automation/custom_app.png
-      :alt: Custom App
+     :alt: Custom App
 
 Webhook Signature Verification
 ------------------------------
@@ -50,14 +50,14 @@ To verify the signature, you should complete the following steps:
 Your Talkable **Webhook security key** can be found in the Webhook set up page by navigating to **Menu** then **Webhooks**.
 
 .. image:: /_static/img/menu_webhooks_screenshot.png
-   :alt: Webhooks Menu Item
+  :alt: Webhooks Menu Item
 
 .. raw:: html
 
-   <hr>
+  <hr>
 
 .. image:: /_static/img/webhook_secret_key.png
-   :alt: Webhook Security Key
+  :alt: Webhook Security Key
 
 **3. Compare the signatures**
 
@@ -69,38 +69,38 @@ Your Talkable **Webhook security key** can be found in the Webhook set up page b
 
 .. code-block:: ruby
 
-   require 'base64'
-   require 'openssl'
-   require 'active_support/security_utils'
+  require 'base64'
+  require 'openssl'
+  require 'active_support/security_utils'
 
-   WEBHOOK_SECRET_KEY = 'my_webhook_secret'
+  WEBHOOK_SECRET_KEY = 'my_webhook_secret'
 
-   def verify_webhook(data, header_signature)
-     calculated_signature = Base64.strict_encode64(OpenSSL::HMAC.hexdigest('sha256', WEBHOOK_SECRET_KEY, data))
-     ActiveSupport::SecurityUtils.secure_compare(calculated_signature, header_signature)
-   end
+  def verify_webhook(data, header_signature)
+    calculated_signature = Base64.strict_encode64(OpenSSL::HMAC.hexdigest('sha256', WEBHOOK_SECRET_KEY, data))
+    ActiveSupport::SecurityUtils.secure_compare(calculated_signature, header_signature)
+  end
 
 *JavaScript:*
 
 .. code-block:: javascript
 
-   const crypto = require('crypto');
+  const crypto = require('crypto');
 
-   const WEBHOOK_SECRET_KEY = 'my_webhook_secret';
+  const WEBHOOK_SECRET_KEY = 'my_webhook_secret';
 
-   function verifyWebhook(data, headerSignature) {
-     // Calculate HMAC
-     const calculatedSignature = btoa(crypto
-       .createHmac('sha256', WEBHOOK_SECRET_KEY)
-       .update(data)
-       .digest('hex')
-     );
+  function verifyWebhook(data, headerSignature) {
+    // Calculate HMAC
+    const calculatedSignature = btoa(crypto
+      .createHmac('sha256', WEBHOOK_SECRET_KEY)
+      .update(data)
+      .digest('hex')
+    );
 
-     return crypto.timingSafeEqual(
-       Buffer.from(calculatedSignature, 'base64'),
-       Buffer.from(headerSignature, 'base64')
-     );
-   }
+    return crypto.timingSafeEqual(
+      Buffer.from(calculatedSignature, 'base64'),
+      Buffer.from(headerSignature, 'base64')
+    );
+  }
 
 Available actions
 -----------------
@@ -108,7 +108,7 @@ Available actions
 Each action allows custom attributes to be included. You can see allowed interpolation variables by clicking `Show available variables` button:
 
 .. image:: /_static/img/email_marketing_and_automation/variables.png
-   :alt: Variables
+  :alt: Variables
 
 Referral Create
 ...............
@@ -119,13 +119,13 @@ Triggers when a new referral is created, sending detailed information about the
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "campaign_id": "142",
-     "referral_status": "in_progress",
-     "advocate_email": "advocate@example.com",
-     "friend_email": "friend@example.com"
-   }
+  {
+    "site_id": "1",
+    "campaign_id": "142",
+    "referral_status": "in_progress",
+    "advocate_email": "advocate@example.com",
+    "friend_email": "friend@example.com"
+  }
 
 Sync signups
 ............
@@ -136,12 +136,12 @@ This action automatically synchronizes all people whenever they sign up no matte
 
 .. code-block:: JSON
 
-   {
-     "email": "person-9eb230f8d189fca9@talkable-sample.com",
-     "email_optin": "true",
-     "phone_number": "+12025551111",
-     "phone_optin": "true"
-   }
+  {
+    "email": "person-9eb230f8d189fca9@talkable-sample.com",
+    "email_optin": "true",
+    "phone_number": "+12025551111",
+    "phone_optin": "true"
+  }
 
 Sync email opt-ins
 ..................
@@ -152,11 +152,11 @@ This action automatically synchronizes all people whenever they sign up and opt
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "person-40728a5b940e3247@talkable-sample.com",
-     "email_optin": "true"
-   }
+  {
+    "site_id": "1",
+    "email": "person-40728a5b940e3247@talkable-sample.com",
+    "email_optin": "true"
+  }
 
 Sync phone opt-ins
 ..................
@@ -167,11 +167,11 @@ This action automatically synchronizes all people whenever they sign up and opt
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "person-fa8e880e25bd47b3@talkable-sample.com",
-     "phone_number": "+12025551111"
-   }
+  {
+    "site_id": "1",
+    "email": "person-fa8e880e25bd47b3@talkable-sample.com",
+    "phone_number": "+12025551111"
+  }
 
 Sync loyalty actions
 ....................
@@ -182,10 +182,10 @@ This action automatically synchronizes all loyalty members whenever they make a
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "loyalty@talkable.com"
-   }
+  {
+    "site_id": "1",
+    "email": "loyalty@talkable.com"
+  }
 
 Sync loyalty tier transitions
 .............................
@@ -196,10 +196,10 @@ This action automatically synchronizes all loyalty members whenever their tier i
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "loyalty@talkable.com"
-   }
+  {
+    "site_id": "1",
+    "email": "loyalty@talkable.com"
+  }
 
 Unsubscribe
 ...........
@@ -210,10 +210,10 @@ Whenever customers unsubscribe from Talkable emails they will also become unsubs
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "person-591542c54ff21a49@talkable-sample.com"
-   }
+  {
+    "site_id": "1",
+    "email": "person-591542c54ff21a49@talkable-sample.com"
+  }
 
 Offer share
 ...........
@@ -224,10 +224,10 @@ Whenever a person shares the offer, the share information will be sent to your E
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "email": "person-591542c54ff21a49@talkable-sample.com"
-   }
+  {
+    "site_id": "1",
+    "email": "person-591542c54ff21a49@talkable-sample.com"
+  }
 
 Send reward
 ...........
@@ -238,13 +238,13 @@ This action sends the reward information to your ESP.
 
 .. code-block:: JSON
 
-   {
-     "description": "$5",
-     "amount": "5.0",
-     "coupon_code": "FR_NEW_5_OFF",
-     "reason": "click",
-     "site_id": "1"
-   }
+  {
+    "description": "$5",
+    "amount": "5.0",
+    "coupon_code": "FR_NEW_5_OFF",
+    "reason": "click",
+    "site_id": "1"
+  }
 
 Create coupon
 .............
@@ -255,11 +255,11 @@ When the quantity of available coupons drops below a Talkable threshold this act
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "coupon_code": "SAMPLE-COUPON-CODE",
-     "coupon_discount_amount": "0.0"
-   }
+  {
+    "site_id": "1",
+    "coupon_code": "SAMPLE-COUPON-CODE",
+    "coupon_discount_amount": "0.0"
+  }
 
 Event
 .....
@@ -270,16 +270,16 @@ Triggers when a new event or purchase is created.
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "type": "Event",
-     "created_at": "2024-11-25 00:00:00 -0800",
-     "event_category": "public_event",
-     "event_number": "183247241",
-     "subtotal": "100.0",
-     "currency_iso_code": "USD",
-     "email": "advocate@example.com"
-   }
+  {
+    "site_id": "1",
+    "type": "Event",
+    "created_at": "2024-11-25 00:00:00 -0800",
+    "event_category": "public_event",
+    "event_number": "183247241",
+    "subtotal": "100.0",
+    "currency_iso_code": "USD",
+    "email": "advocate@example.com"
+  }
 
 Referral status change
 ......................
@@ -290,13 +290,13 @@ This action is triggered when referral’s status changes.
 
 .. code-block:: JSON
 
-   {
-     "site_id": "1",
-     "campaign_id": "142",
-     "referral_status": "in_progress",
-     "advocate_email": "advocate@example.com",
-     "friend_email": "friend@example.com"
-   }
+  {
+    "site_id": "1",
+    "campaign_id": "142",
+    "referral_status": "in_progress",
+    "advocate_email": "advocate@example.com",
+    "friend_email": "friend@example.com"
+  }
 
 Click reward verification
 .........................
@@ -309,10 +309,10 @@ This action sends information about a Friend when they attempt claiming a reward
 
 .. code-block:: JSON
 
-   {
-     "email": "friend@example.com",
-     "site_id": "1"
-   }
+  {
+    "email": "friend@example.com",
+    "site_id": "1"
+  }
 
 
 Testing
@@ -326,7 +326,7 @@ Testing Custom app actions can be accomplished with the help of Webhook Tester,
 4. Click **Send sample payload** near the action you want to test.
 
    .. image:: /_static/img/email_marketing_and_automation/send_sample_payload.png
-      :alt: Send sample payload
+     :alt: Send sample payload
 
 5. After you finish the implementation on your site **change Webhook Tester URL
    to the live URL** in your Custom app.
@@ -339,6 +339,6 @@ In case your servers are behind firewall, you may need to whitelist Talkable IP
 addresses so webhooks can be delivered. Pass list of these addresses to your network administrator:
 
 .. hlist::
-   :columns: 4
+  :columns: 4
 
-   .. include:: /partials/talkable_ip_list.rst
+  .. include:: /partials/talkable_ip_list.rst
diff --git a/source/email_marketing_and_automation/exponea.rst b/source/email_marketing_and_automation/exponea.rst
index c40dfc2cc..aa94fe0b8 100644
--- a/source/email_marketing_and_automation/exponea.rst
+++ b/source/email_marketing_and_automation/exponea.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to Exponea for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to Exponea for email marketing and automation.
 
 Exponea
 =======
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to Exponea, supporting enhan
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/getresponse.rst b/source/email_marketing_and_automation/getresponse.rst
index bae74c029..70da36be8 100644
--- a/source/email_marketing_and_automation/getresponse.rst
+++ b/source/email_marketing_and_automation/getresponse.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to GetResponse for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to GetResponse for email marketing and automation.
 
 GetResponse
 ===========
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to GetResponse, streamlining
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/hubspot.rst b/source/email_marketing_and_automation/hubspot.rst
index 1157e8287..80f3a6c9e 100644
--- a/source/email_marketing_and_automation/hubspot.rst
+++ b/source/email_marketing_and_automation/hubspot.rst
@@ -38,17 +38,17 @@ Please use the following guide to start using an app you need:
 1. Navigate into the App store:
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+    :alt: App store step 1
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/hubspot.jpg
-      :alt: hubspot
+    :alt: hubspot
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/iterable.rst b/source/email_marketing_and_automation/iterable.rst
index 994dfab5f..0b689687d 100644
--- a/source/email_marketing_and_automation/iterable.rst
+++ b/source/email_marketing_and_automation/iterable.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with Iterable integration.
+  :description: Synchronize Talkable collected emails with Iterable integration.
 
 Iterable
 ========
diff --git a/source/email_marketing_and_automation/klaviyo.rst b/source/email_marketing_and_automation/klaviyo.rst
index d0b799d7c..2a3ac830a 100644
--- a/source/email_marketing_and_automation/klaviyo.rst
+++ b/source/email_marketing_and_automation/klaviyo.rst
@@ -38,17 +38,17 @@ Please use the following guide to start using an app you need:
 1. Navigate into the App store:
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+    :alt: App store step 1
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/klaviyo.png
-      :alt: klaviyo
+    :alt: klaviyo
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/listrak.rst b/source/email_marketing_and_automation/listrak.rst
index 638469a6a..b1f63b67c 100644
--- a/source/email_marketing_and_automation/listrak.rst
+++ b/source/email_marketing_and_automation/listrak.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails and phone numbers with Listrak integration for email marketing and SMS rewards.
+  :description: Synchronize Talkable collected emails and phone numbers with Listrak integration for email marketing and SMS rewards.
 
 Listrak
 =======
@@ -17,4 +17,4 @@ Talkable offers seamless integration with Listrak to enhance your marketing and
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/mailchimp.rst b/source/email_marketing_and_automation/mailchimp.rst
index 4513eddef..16ab1aa00 100644
--- a/source/email_marketing_and_automation/mailchimp.rst
+++ b/source/email_marketing_and_automation/mailchimp.rst
@@ -41,14 +41,14 @@ Please use the following guide to start using an app you need:
     :alt: App store step 1
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/mailchimp.png
-      :alt: mailchimp
+    :alt: mailchimp
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/omnisend.rst b/source/email_marketing_and_automation/omnisend.rst
index 6ccf8e6ea..145cbb477 100644
--- a/source/email_marketing_and_automation/omnisend.rst
+++ b/source/email_marketing_and_automation/omnisend.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to Omnisend for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to Omnisend for email marketing and automation.
 
 Omnisend
 ========
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to Omnisend, enabling stream
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/oracle_bronto.rst b/source/email_marketing_and_automation/oracle_bronto.rst
index 28388ab4c..7a7672e13 100644
--- a/source/email_marketing_and_automation/oracle_bronto.rst
+++ b/source/email_marketing_and_automation/oracle_bronto.rst
@@ -38,17 +38,17 @@ Please use the following guide to start using an app you need:
 1. Navigate into the App store:
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+    :alt: App store step 1
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/oracle_bronto.jpg
-      :alt: Oracle Bronto
+    :alt: Oracle Bronto
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/sailthru.rst b/source/email_marketing_and_automation/sailthru.rst
index af8417e3f..fc5ff7191 100644
--- a/source/email_marketing_and_automation/sailthru.rst
+++ b/source/email_marketing_and_automation/sailthru.rst
@@ -38,17 +38,17 @@ Please use the following guide to start using an app you need:
 1. Navigate into the App store:
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_1.png
-      :alt: App store step 1
+    :alt: App store step 1
 
   .. image:: /_static/img/email_marketing_and_automation/app_store_step_2.png
-      :alt: App store step 2
+    :alt: App store step 2
 
 2. Choose an app you need by clicking “Install”
 3. Fill in all necessary fields. You can use tips on the right that instruct how to find all necessary credentials.
 4. Complete installation and enable the app:
 
   .. image:: /_static/img/email_marketing_and_automation/sailthru.jpg
-      :alt: Sailthru
+    :alt: Sailthru
 
 5. Test the app by pressing on the “Send sample payload” and then check if you are seeing a test request inside your ESP:
 
diff --git a/source/email_marketing_and_automation/sendgrid.rst b/source/email_marketing_and_automation/sendgrid.rst
index e98b9ea33..c90a8fe26 100644
--- a/source/email_marketing_and_automation/sendgrid.rst
+++ b/source/email_marketing_and_automation/sendgrid.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with Sendgrid integration.
+  :description: Synchronize Talkable collected emails with Sendgrid integration.
 
 Sendgrid
 ========
@@ -11,4 +11,4 @@ With this integration, Talkable synchronizes all people who opt in for Talkable
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/sfmc.rst b/source/email_marketing_and_automation/sfmc.rst
index 9400fc4a3..a16f47fa1 100644
--- a/source/email_marketing_and_automation/sfmc.rst
+++ b/source/email_marketing_and_automation/sfmc.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with Salesforce Marketing Cloud integration.
+  :description: Synchronize Talkable collected emails with Salesforce Marketing Cloud integration.
 
 Salesforce Marketing Cloud
 ==========================
@@ -11,4 +11,4 @@ With this integration, Talkable synchronizes all people who opt in for Talkable
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/targetbay.rst b/source/email_marketing_and_automation/targetbay.rst
index f5e91fdd0..33926efc3 100644
--- a/source/email_marketing_and_automation/targetbay.rst
+++ b/source/email_marketing_and_automation/targetbay.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize email opt-ins collected with Talkable to TargetBay for email marketing and automation.
+  :description: Synchronize email opt-ins collected with Talkable to TargetBay for email marketing and automation.
 
 TargetBay
 =========
@@ -11,4 +11,4 @@ With this integration, Talkable syncs email opt-ins to TargetBay, enhancing cust
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/email_marketing_and_automation/what_counts_pro.rst b/source/email_marketing_and_automation/what_counts_pro.rst
index 337ab540d..80350a3da 100644
--- a/source/email_marketing_and_automation/what_counts_pro.rst
+++ b/source/email_marketing_and_automation/what_counts_pro.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Synchronize Talkable collected emails with WhatCounts integration.
+  :description: Synchronize Talkable collected emails with WhatCounts integration.
 
 WhatCounts
 ==========
diff --git a/source/index.rst b/source/index.rst
index 614fecdab..9e15090c5 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -6,7 +6,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable campaigns, features and integration docs for referral program launch and settings.
+  :description: Talkable campaigns, features and integration docs for referral program launch and settings.
 
 Talkable Basics
 ===============
diff --git a/source/integration/custom/cookies.rst b/source/integration/custom/cookies.rst
index a5621c4d7..e8b3d86c2 100644
--- a/source/integration/custom/cookies.rst
+++ b/source/integration/custom/cookies.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This is all about how we use cookies.
+  :description: This is all about how we use cookies.
 
 Cookies
 #######
@@ -33,40 +33,40 @@ These cookies and other technologies help us learn how well our Campaigns and Se
 We use these cookies to understand, improve, and research our Site and Services.
 
 .. list-table::
-   :widths: 30 30 30 10
-   :header-rows: 1
-
-   * - Cookie name
-     - Purpose
-     - Domain(s)
-     - Retention period(Days)
-   * - ``tkbl_session_id``
-     - Strictly Necessary
-     - | talkable.com
-       | shop domain
-     - 0
-   * - ``tkbl_session``
-     - Functionality
-     - | talkable.com
-       | shop domain
-     - 400
-   * - ``tkbl_cvuuid``
-     - Functionality
-     - | talkable.com
-       | shop domain
-     - 400
-   * - `multiple <https://newrelic.com/termsandconditions/cookie-policy/cookie-table>`_
-     - Analytics and Performance
-     - \*.newrelic.com
-     - 0-400
-   * - ``bugsnag*``
-     - Analytics and Performance
-     - \*.bugsnag.com
-     - 0-400
-   * - ``_ga``
-     - Analytics and Performance
-     - talkable.com
-     - 400
+  :widths: 30 30 30 10
+  :header-rows: 1
+
+  * - Cookie name
+    - Purpose
+    - Domain(s)
+    - Retention period(Days)
+  * - ``tkbl_session_id``
+    - Strictly Necessary
+    - | talkable.com
+      | shop domain
+    - 0
+  * - ``tkbl_session``
+    - Functionality
+    - | talkable.com
+      | shop domain
+    - 400
+  * - ``tkbl_cvuuid``
+    - Functionality
+    - | talkable.com
+      | shop domain
+    - 400
+  * - `multiple <https://newrelic.com/termsandconditions/cookie-policy/cookie-table>`_
+    - Analytics and Performance
+    - \*.newrelic.com
+    - 0-400
+  * - ``bugsnag*``
+    - Analytics and Performance
+    - \*.bugsnag.com
+    - 0-400
+  * - ``_ga``
+    - Analytics and Performance
+    - talkable.com
+    - 400
 
 .. _integration/custom/cookies/gdpr_and_ccpa_compliance:
 
@@ -79,8 +79,7 @@ Under GDPR and CCPA, setting such cookies does not require user consent.
 Post-consent (e.g., during signup), Talkable activates standard cookies to monitor user activities, aligning with regulatory guidelines.
 
 .. note::
-   Limitations of compliance mode seriously hinders Talkable ability to track referrals and conversions.
-   It is advised to use compliant mode only if you are legally obligated to do so.
+  Limitations of compliance mode seriously hinders Talkable ability to track referrals and conversions.
+  It is advised to use compliant mode only if you are legally obligated to do so.
 
 To enable GDPR and CCPA compliant mode, please contact your Customer Success Manager.
-
diff --git a/source/integration/custom/integration_components.rst b/source/integration/custom/integration_components.rst
index e2599299b..6e62e8e49 100644
--- a/source/integration/custom/integration_components.rst
+++ b/source/integration/custom/integration_components.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Find the components of what Talkable is composed.
+  :description: Find the components of what Talkable is composed.
 
 Integration Components
 ======================
@@ -67,29 +67,29 @@ script.
 
 .. code-block:: html
 
-   <!-- Begin Talkable integration code -->
-   <script async src="https://d2jjzw81hqbuqv.cloudfront.net/integration/clients/<YOUR-TALKABLE-SITE-ID>.min.js"></script>
-   <script>
-     window._talkableq = window._talkableq || [];
-     window._talkableq.unshift(['init', { site_id: '<YOUR-TALKABLE-SITE-ID>' }]);
-     window._talkableq.push(['authenticate_customer', {
-       email: '', // Optional - Email of the customer, if available. Example: 'customer@example.com'
-       phone_number: '', // Optional - Customer's phone number. Example: '+12025551111'
-       first_name: '', // Optional - First name of the customer. Example: 'John'
-       last_name: '', // Optional - Last name of the customer. Example: 'Smith'
-       traffic_source: '', // Optional - Traffic source that led to the campaign. Example: 'facebook'
-       segment1: '', // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-       segment2: '', // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-       segment3: '' // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
-     }]);
-   </script>
-   <!-- End Talkable integration code -->
+  <!-- Begin Talkable integration code -->
+  <script async src="https://d2jjzw81hqbuqv.cloudfront.net/integration/clients/<YOUR-TALKABLE-SITE-ID>.min.js"></script>
+  <script>
+    window._talkableq = window._talkableq || [];
+    window._talkableq.unshift(['init', { site_id: '<YOUR-TALKABLE-SITE-ID>' }]);
+    window._talkableq.push(['authenticate_customer', {
+      email: '', // Optional - Email of the customer, if available. Example: 'customer@example.com'
+      phone_number: '', // Optional - Customer's phone number. Example: '+12025551111'
+      first_name: '', // Optional - First name of the customer. Example: 'John'
+      last_name: '', // Optional - Last name of the customer. Example: 'Smith'
+      traffic_source: '', // Optional - Traffic source that led to the campaign. Example: 'facebook'
+      segment1: '', // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+      segment2: '', // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+      segment3: '' // Optional - Custom segment (e.g., location, age group, source channel, platform, gender, interests).
+    }]);
+  </script>
+  <!-- End Talkable integration code -->
 
 In this example, `segment1`, `segment2`, and `segment3` attributes are passed through `authenticate_customer` to enable segmentation without requiring an Origin creation.
 
 .. note::
 
-   Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
+  Segments can also be passed in `register_affiliate`, `register_purchase`, and `register_event`, providing flexibility for different integration scenarios.
 
 This approach simplifies custom data handling for customers, allowing for unified data across various methods and optimizing segmentation management without additional calls.
 
@@ -101,7 +101,7 @@ Initialization Script Notes
    here:
 
    .. figure:: /_static/img/site_id.png
-      :alt: Site ID
+     :alt: Site ID
 
 2. **Variables.** Use your dynamic variables to pass user details {email,
    first_name, last_name} if the user is logged in and the data
@@ -153,7 +153,7 @@ Post Purchase Script Notes
 
 .. note::
 
-   All PII params support data encryption. Find more about :ref:`Params Encryption <advanced_features/params_encryption>`.
+  All PII params support data encryption. Find more about :ref:`Params Encryption <advanced_features/params_encryption>`.
 
 .. _integration/custom/integration_components/advocate_landing_page:
 
@@ -165,7 +165,7 @@ in the body of the page between your standard site header and footer:
 
 .. code-block:: html
 
-   <div id="talkable-offer"></div>
+  <div id="talkable-offer"></div>
 
 Advocate Landing Page Notes
 ---------------------------
@@ -183,7 +183,7 @@ Advocate Landing Page Notes
    `https://www.admin.talkable.com/sites/<YOUR-TALKABLE-SITE-ID>/placements:`
 
    .. figure:: /_static/img/placement_edit.png
-      :alt: Placement Edit
+     :alt: Placement Edit
 
 |hr|
 
@@ -198,7 +198,7 @@ the body of the page:
 
 .. code-block:: html
 
-   <div id="talkable-offer"></div>
+  <div id="talkable-offer"></div>
 
 Referral Dashboard Notes
 ------------------------
@@ -230,7 +230,7 @@ Referral Dashboard Notes
 
 .. container:: hidden
 
- .. toctree::
+  .. toctree::
 
     Alternate Post Purchase Script for cart line item passing <alternate_post_purchase>
     Integrating with a Tag Manager <integration_tag_manager>
diff --git a/source/integration/custom/integration_tag_manager.rst b/source/integration/custom/integration_tag_manager.rst
index 68c87d29d..eab4934de 100644
--- a/source/integration/custom/integration_tag_manager.rst
+++ b/source/integration/custom/integration_tag_manager.rst
@@ -53,9 +53,9 @@ Best Practices for Speed Optimization
 4. Implementing a custom domain for your integration won't directly increase its speed, but it will significantly reduce issues related to incognito mode and security policies blocking for third-party content.
 
 .. note:: 
-   If you use GTM, you can add `priority <https://support.google.com/tagmanager/answer/2772421>`_ to the tag. The higher the priority, the quicker it gets loaded.
+  If you use GTM, you can add `priority <https://support.google.com/tagmanager/answer/2772421>`_ to the tag. The higher the priority, the quicker it gets loaded.
 
-   .. image:: /_static/img/gtm-priority.png
+  .. image:: /_static/img/gtm-priority.png
 
 Alternative Approach: Direct Integration
 ----------------------------------------
@@ -100,7 +100,7 @@ If you've decided to remove the Talkable integration script from GTM, follow the
 **Important Note:** After removing the Talkable integration script from GTM, you'll need to implement the :ref:`direct integration approach <integration/custom/integration_components>` documented earlier to ensure Talkable functionality on your website.
 
 .. note::
-   Talkable doesn't recommend adding integration as tags in Google Tag Manager because of slow loading of campaigns for certain user agents as well as GTM being blocked by some Ad blockers
+  Talkable doesn't recommend adding integration as tags in Google Tag Manager because of slow loading of campaigns for certain user agents as well as GTM being blocked by some Ad blockers
 
 Helpful Links
 -------------
diff --git a/source/integration/custom/overview.rst b/source/integration/custom/overview.rst
index 8ba24a744..7dfb42d4a 100644
--- a/source/integration/custom/overview.rst
+++ b/source/integration/custom/overview.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can integrate Talkable referral marketing platform to e-commerce sites in a few quick steps.
+  :description: You can integrate Talkable referral marketing platform to e-commerce sites in a few quick steps.
 
 Integration High-Level Overview
 ===============================
@@ -12,17 +12,17 @@ a few quick steps by adding the below scripts to your site.
 
  .. note::
 
-    All design and referral campaign setup is done inside the Talkable platform,
-    then via ‘iframe’ referral campaign content is injected into the e-commerce
-    site. The below scripts also handle the collection of specific necessary user
-    data for Talkable to service the referral campaigns.
+   All design and referral campaign setup is done inside the Talkable platform,
+   then via ‘iframe’ referral campaign content is injected into the e-commerce
+   site. The below scripts also handle the collection of specific necessary user
+   data for Talkable to service the referral campaigns.
 
-    Site-specific integration scripts are found after logging in at
-    ``https://www.admin.talkable.com/sites/<YOUR-TALKABLE-SITE-ID>/integration/other``
+   Site-specific integration scripts are found after logging in at
+   ``https://www.admin.talkable.com/sites/<YOUR-TALKABLE-SITE-ID>/integration/other``
 
 .. raw:: html
 
-   <h2>Integration Steps</h2>
+  <h2>Integration Steps</h2>
 
 1. Add the :ref:`Talkable Initialization Script <integration/custom/integration_components/initialization_script>`
    to your header or any template spanning every page. Surface variables for
@@ -37,12 +37,12 @@ a few quick steps by adding the below scripts to your site.
 
  .. note::
 
-    If a business has both one-time purchases and subscription transactions, or
-    the business has a strictly subscription or SaaS model we recommend integrating
-    the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
+   If a business has both one-time purchases and subscription transactions, or
+   the business has a strictly subscription or SaaS model we recommend integrating
+   the ‘Post Purchase’ through Events. :ref:`Learn more <advanced_features/events>`.
 
-    Post Purchase step is the only step which changes for subscription business
-    model integration - other steps remain the same.
+   Post Purchase step is the only step which changes for subscription business
+   model integration - other steps remain the same.
 
 3. To host the Invite Standalone campaign, create a new HTML page with standard
    header/footer. Best practice is to create this page on ``www.your-site.com/share``
@@ -54,7 +54,7 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-      <div id="talkable-offer"></div>
+     <div id="talkable-offer"></div>
 
 4. To host the Advocate Dashboard Standalone campaign, create an additional new
    HTML page under your user accounts section behind login.
@@ -66,4 +66,4 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-      <div id="talkable-offer"></div>
+     <div id="talkable-offer"></div>
diff --git a/source/integration/custom/questions.rst b/source/integration/custom/questions.rst
index 7fe8e7be0..bd22626d9 100644
--- a/source/integration/custom/questions.rst
+++ b/source/integration/custom/questions.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This is a collection of your Frequently Asked Questions (FAQs). If your question isn’t in this list, just ask us.
+  :description: This is a collection of your Frequently Asked Questions (FAQs). If your question isn’t in this list, just ask us.
 
 F.A.Q.
 ======
diff --git a/source/integration/custom/validating_integration.rst b/source/integration/custom/validating_integration.rst
index a3385f026..051604ce2 100644
--- a/source/integration/custom/validating_integration.rst
+++ b/source/integration/custom/validating_integration.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: This is all about validating integration, from a checklist to testing.
+  :description: This is all about validating integration, from a checklist to testing.
 
 Validating the Integration
 ==========================
@@ -66,8 +66,8 @@ There are 5 types:
 5. :underline:`Claim by Name` displays as a floating widget button on your checkout page.
 
    .. note::
-      Claim by Name campaign has its own DIV container and can be shown along with the Floating Widget on the same page.
-      The DIV id is `talkable-claim-by-name`.
+     Claim by Name campaign has its own DIV container and can be shown along with the Floating Widget on the same page.
+     The DIV id is `talkable-claim-by-name`.
 
 -  :underline:`How to create campaigns:` Here’s a video showing you how to quickly
    create all campaigns in less than 1 minute
@@ -110,4 +110,4 @@ eligible for test mode display. Use the following image as a visual
 guideline:
 
 .. figure:: /_static/img/campaigns_dashboard.png
-   :alt: Campaigns
+  :alt: Campaigns
diff --git a/source/integration/custom_integration.rst b/source/integration/custom_integration.rst
index cdb868f43..92ed73a5a 100644
--- a/source/integration/custom_integration.rst
+++ b/source/integration/custom_integration.rst
@@ -2,14 +2,14 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Learn all the ins and outs of integration. It’s easier than it seems.
+  :description: Learn all the ins and outs of integration. It’s easier than it seems.
 
 Standard Integration
 ####################
 
 .. raw:: html
 
-   <h2 class="mts">Integration High Level Overview</h2>
+  <h2 class="mts">Integration High Level Overview</h2>
 
 1. Add the :ref:`Talkable Initialization Script <integration/custom/integration_components/initialization_script>`
    to your header or any template spanning every page.
@@ -34,14 +34,14 @@ Standard Integration
 
   .. toctree::
 
-     custom/overview
+    custom/overview
 
 Contents:
 
 .. toctree::
 
-   custom/integration_components
-   custom/validating_integration
-   verify
-   custom/cookies
-   custom/questions
+  custom/integration_components
+  custom/validating_integration
+  verify
+  custom/cookies
+  custom/questions
diff --git a/source/integration/ecommerce_platforms.rst b/source/integration/ecommerce_platforms.rst
index e9092dd78..8b5e4fa2e 100644
--- a/source/integration/ecommerce_platforms.rst
+++ b/source/integration/ecommerce_platforms.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: E-commerce Platforms include all Talkable integration.
+  :description: E-commerce Platforms include all Talkable integration.
 
 E-commerce Platforms
 ####################
@@ -10,7 +10,7 @@ E-commerce Platforms
 Contents:
 
 .. toctree::
-    ecommerce_platforms/bigcommerce
-    ecommerce_platforms/demandware
-    ecommerce_platforms/shopify
-    ecommerce_platforms/magento
+  ecommerce_platforms/bigcommerce
+  ecommerce_platforms/demandware
+  ecommerce_platforms/shopify
+  ecommerce_platforms/magento
diff --git a/source/integration/ecommerce_platforms/bigcommerce.rst b/source/integration/ecommerce_platforms/bigcommerce.rst
index 620a0aefe..80e3ea3ad 100644
--- a/source/integration/ecommerce_platforms/bigcommerce.rst
+++ b/source/integration/ecommerce_platforms/bigcommerce.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: BigCommerce integration allows synchronizing coupons to BigCommerce with webhook support.
+  :description: BigCommerce integration allows synchronizing coupons to BigCommerce with webhook support.
 
 BigCommerce
 ===========
diff --git a/source/integration/ecommerce_platforms/demandware.rst b/source/integration/ecommerce_platforms/demandware.rst
index 7762f2af6..3c933706a 100644
--- a/source/integration/ecommerce_platforms/demandware.rst
+++ b/source/integration/ecommerce_platforms/demandware.rst
@@ -2,14 +2,14 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable cartridge is a self-contained cartridge, which you can easily integrate into any Salesforce B2C Commerce Cloud store.
+  :description: Talkable cartridge is a self-contained cartridge, which you can easily integrate into any Salesforce B2C Commerce Cloud store.
 
 Salesforce B2C Commerce Cloud Integration
 =========================================
 
 .. note::
 
-   You must have Talkable account in order to get started
+  You must have Talkable account in order to get started
 
 Talkable cartridge is a self-contained cartridge that can easily integrate
 into any B2C Commerce Cloud store. The cartridge can be configured in
diff --git a/source/integration/ecommerce_platforms/magento.rst b/source/integration/ecommerce_platforms/magento.rst
index 1696e8076..b548c49b8 100644
--- a/source/integration/ecommerce_platforms/magento.rst
+++ b/source/integration/ecommerce_platforms/magento.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable offers free extensions for Magento 1.x and Magento 2.x. Now you can integrate and use Talkable with your Magento store.
+  :description: Talkable offers free extensions for Magento 1.x and Magento 2.x. Now you can integrate and use Talkable with your Magento store.
 
 Magento Integration
 *******************
@@ -38,9 +38,9 @@ To check your Magento version, navigate to your store's admin panel. The version
 
   .. toctree::
 
-     magento/magento1
-     magento/magento2
+    magento/magento1
+    magento/magento2
 
 **Contact us**
 
-Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
\ No newline at end of file
+Interested in setting this up? Contact your CSM or get in touch `here <https://lp.talkable.com/lets-talk-referral>`_.
diff --git a/source/integration/ecommerce_platforms/magento/magento1.rst b/source/integration/ecommerce_platforms/magento/magento1.rst
index f8cad7369..288865c57 100644
--- a/source/integration/ecommerce_platforms/magento/magento1.rst
+++ b/source/integration/ecommerce_platforms/magento/magento1.rst
@@ -2,17 +2,17 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: A Magento Talkable extension is available for easy integration. The extension supports Magento versions 1.5+
+  :description: A Magento Talkable extension is available for easy integration. The extension supports Magento versions 1.5+
 
 Magento 1.x Integration
 =======================
 .. warning::
 
-   Magento 1 is not supported from July 1st, 2020.
+  Magento 1 is not supported from July 1st, 2020.
 
 .. note::
 
-   You must have Talkable account in order to get started
+  You must have Talkable account in order to get started
 
 A `Magento Talkable extension`_ is available for easy
 integration. The extension currently supports Magento versions 1.5+
@@ -50,7 +50,7 @@ integration. The extension currently supports Magento versions 1.5+
 
 .. raw:: html
 
-   <h2>Troubleshooting</h2>
+  <h2>Troubleshooting</h2>
 
 In case you cannot find Talkable extension in the sidebar try clearing cache:
 
diff --git a/source/integration/ecommerce_platforms/magento/magento2.rst b/source/integration/ecommerce_platforms/magento/magento2.rst
index 1e2050664..e73367985 100644
--- a/source/integration/ecommerce_platforms/magento/magento2.rst
+++ b/source/integration/ecommerce_platforms/magento/magento2.rst
@@ -2,17 +2,17 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: The Magento 2 Integration Extension is available to download in the Magento Marketplace. The extension supports all versions of Magento 2.0 or higher.
+  :description: The Magento 2 Integration Extension is available to download in the Magento Marketplace. The extension supports all versions of Magento 2.0 or higher.
 
 Magento 2.x Integration
 =======================
 
 .. note::
 
-   To get started, you must have an account created with Talkable, and a Magento Marketplace account.
-   If you do not have a Magento Marketplace account configured, follow
-   `these steps <https://docs.magento.com/user-guide/magento/magento-marketplace.html#marketplace-credentials>`_
-   to connect one to your Magento store.
+  To get started, you must have an account created with Talkable, and a Magento Marketplace account.
+  If you do not have a Magento Marketplace account configured, follow
+  `these steps <https://docs.magento.com/user-guide/magento/magento-marketplace.html#marketplace-credentials>`_
+  to connect one to your Magento store.
 
 The `Magento 2 Integration Extension`_ is available to download in the Magento Marketplace.
 The extension supports all versions of Magento 2.0 or higher.
@@ -24,8 +24,8 @@ Installation
 
 .. note::
 
-   Installation via Composer requires an IT administrator with SSH access to the server where Magento 2 is hosted.
-   To install the Talkable extension, you’ll need to execute four commands.
+  Installation via Composer requires an IT administrator with SSH access to the server where Magento 2 is hosted.
+  To install the Talkable extension, you’ll need to execute four commands.
 
 1. Visit the Magento Marketplace and get the `Talkable extension`_.
 
@@ -38,38 +38,38 @@ Installation
 
     .. code-block:: bash
 
-       composer require talkable/magento2-integration
+      composer require talkable/magento2-integration
 
 4. Run the following command to enable the Talkable extension you just downloaded:
 
     .. code-block:: bash
 
-       php bin/magento module:enable Talkable_Integration --clear-static-content
+      php bin/magento module:enable Talkable_Integration --clear-static-content
 
    You should see the following output:
 
     .. code-block::
 
-        The following modules have been enabled:
-        - Talkable_Integration
+      The following modules have been enabled:
+      - Talkable_Integration
 
-        To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
-        Cache cleared successfully.
-        Generated classes cleared successfully.
-        Please run the 'setup:di:compile' command to generate classes.
-        Generated static view files cleared successfully.
+      To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
+      Cache cleared successfully.
+      Generated classes cleared successfully.
+      Please run the 'setup:di:compile' command to generate classes.
+      Generated static view files cleared successfully.
 
 5. As displayed in the sample output, you must now enable any additional modules. Run the following command to enable them:
 
     .. code-block:: bash
 
-        php bin/magento setup:upgrade
+      php bin/magento setup:upgrade
 
 6. To ensure that the CSS and JS on your Magento 2 store continues to work properly, you’ll need to run a static content deploy command.
 
     .. code-block:: bash
 
-        php bin/magento setup:static-content:deploy -f
+      php bin/magento setup:static-content:deploy -f
 
 7. Installation via Composer is complete! You can now return to the Magento admin dashboard from your browser.
 
@@ -109,19 +109,19 @@ to your Talkable account.
 
 .. warning::
 
-   Only change this setting if you need to connect your store to a different site in the Talkable dashboard.
-   An incorrect value will prevent your campaigns from showing.
+  Only change this setting if you need to connect your store to a different site in the Talkable dashboard.
+  An incorrect value will prevent your campaigns from showing.
 
-   Changing the Site ID will invalidate the full page cache. Magento will display a warning message with
-   a link to the Cache Management page. Please follow this link and refresh the invalidated cache types.
+  Changing the Site ID will invalidate the full page cache. Magento will display a warning message with
+  a link to the Cache Management page. Please follow this link and refresh the invalidated cache types.
 
-   .. image:: /_static/img/magento2/cache.jpg
+  .. image:: /_static/img/magento2/cache.jpg
 
 .. note::
 
-   You need to paste the Site ID from your Talkable Site Dashboard into this field.
+  You need to paste the Site ID from your Talkable Site Dashboard into this field.
 
-   .. image:: /_static/img/magento2/configure3.jpg
+  .. image:: /_static/img/magento2/configure3.jpg
 
 |page_break|
 
@@ -147,8 +147,8 @@ Default values correspond to default placements in Talkable.
 
 .. warning::
 
-   Only change these settings if you have configured custom placements for these campaign types
-   in your Talkable dashboard. Incorrect values will prevent your Standalone or Dashboard campaign from showing.
+  Only change these settings if you have configured custom placements for these campaign types
+  in your Talkable dashboard. Incorrect values will prevent your Standalone or Dashboard campaign from showing.
 
 .. image:: /_static/img/magento2/configure6.jpg
 
diff --git a/source/integration/ecommerce_platforms/shopify.rst b/source/integration/ecommerce_platforms/shopify.rst
index fc981153a..01b1604d3 100644
--- a/source/integration/ecommerce_platforms/shopify.rst
+++ b/source/integration/ecommerce_platforms/shopify.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Here’s how you can integrate Talkable Shopify app with your store.
+  :description: Here’s how you can integrate Talkable Shopify app with your store.
 
 Shopify Integration
 ===================
@@ -14,9 +14,9 @@ Automatic integration
 
   .. note::
 
-     If you have previously integrated with Talkable, make sure you remove the manual
-     Talkable integration script located in the Additional Content & Scripts section before
-     you start the Automatic integration process. See `Manual integration`_ for details.
+    If you have previously integrated with Talkable, make sure you remove the manual
+    Talkable integration script located in the Additional Content & Scripts section before
+    you start the Automatic integration process. See `Manual integration`_ for details.
 
 1. Contact sales@talkable.com to learn about our pricing and set up an account with Talkable
 
@@ -31,10 +31,10 @@ Automatic integration
 
   .. note::
 
-     Post Purchase campaign is located at the “Thank you” page after Checkout.
+    Post Purchase campaign is located at the “Thank you” page after Checkout.
 
-     To check how Standalone Campaign looks visit */pages/share* or */pages/invite* links of your store.
-     You can edit these links in Administrative panel of your store.
+    To check how Standalone Campaign looks visit */pages/share* or */pages/invite* links of your store.
+    You can edit these links in Administrative panel of your store.
 
 .. _integration/ecommerce_platforms/shopify/manual_integration:
 
@@ -77,7 +77,7 @@ please follow the instructions below.
 
           .. code-block:: liquid
 
-             {% render "talkable-partial" %}
+            {% render "talkable-partial" %}
 
         * Click “Save”
 
@@ -92,13 +92,13 @@ please follow the instructions below.
 
           .. code-block:: html
 
-             <div id="talkable-offer"></div>
+            <div id="talkable-offer"></div>
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral campaign“
 
           .. image:: /_static/img/shopify/editor_section.png
-             :alt: Shopify editor - talkable-campaign section
-             :class: is-minimal
+            :alt: Shopify editor - talkable-campaign section
+            :class: is-minimal
 
         * Click “Save”
 
@@ -110,15 +110,15 @@ please follow the instructions below.
         * Change the type of the main section to `talkable-campaign`
 
           .. image:: /_static/img/shopify/editor_template.png
-             :alt: Shopify editor - Talkable page section
-             :class: is-minimal
+            :alt: Shopify editor - Talkable page section
+            :class: is-minimal
 
           .. important::
-             The name of the section should be the same as the one you used
-             in the previous step when naming your section file.
+            The name of the section should be the same as the one you used
+            in the previous step when naming your section file.
 
           .. important::
-             If your main section is disabled, remove the row that does it.
+            If your main section is disabled, remove the row that does it.
 
     3. Create a page:
 
@@ -140,13 +140,13 @@ please follow the instructions below.
 
           .. code-block:: html
 
-             {% if shop.customer_accounts_enabled %}
-               {% if customer %}
-                 <div id="talkable-offer"></div>
-               {% else %}
-                 {{ 'Log in' | customer_login_link }}
-               {% endif %}
-             {% endif %}
+            {% if shop.customer_accounts_enabled %}
+              {% if customer %}
+                <div id="talkable-offer"></div>
+              {% else %}
+                {{ 'Log in' | customer_login_link }}
+              {% endif %}
+            {% endif %}
 
         * Optionally, update the schema name to anything meaningful, for example, “Referral dashboard“
         * Click “Save”
@@ -160,20 +160,20 @@ please follow the instructions below.
 
           .. code-block:: JSON
 
-             {
-               "sections": {
-                 "main": {
-                   "type": "talkable-dashboard"
-                 }
-               }
-             }
+            {
+              "sections": {
+                "main": {
+                  "type": "talkable-dashboard"
+                }
+              }
+            }
 
           .. important::
-             The name of the section should be the same as the one you used
-             in the previous step when naming your section file.
+            The name of the section should be the same as the one you used
+            in the previous step when naming your section file.
 
           .. important::
-             If your main section is disabled, remove the row that does it.
+            If your main section is disabled, remove the row that does it.
 
     3. Create a page:
 
@@ -234,7 +234,7 @@ please follow the instructions below.
 
           .. code-block:: liquid
 
-             {% render "talkable-partial" %}
+            {% render "talkable-partial" %}
 
         * Click “Save”
 
@@ -249,7 +249,7 @@ please follow the instructions below.
 
           .. code-block:: html
 
-             <div id="talkable-offer"></div>
+            <div id="talkable-offer"></div>
 
         * Click “Save”
 
@@ -273,13 +273,13 @@ please follow the instructions below.
 
           .. code-block:: html
 
-             {% if shop.customer_accounts_enabled %}
-               {% if customer %}
-                 <div id="talkable-offer"></div>
-               {% else %}
-                 {{ 'Log in' | customer_login_link }}
-               {% endif %}
-             {% endif %}
+            {% if shop.customer_accounts_enabled %}
+              {% if customer %}
+                <div id="talkable-offer"></div>
+              {% else %}
+                {{ 'Log in' | customer_login_link }}
+              {% endif %}
+            {% endif %}
 
         * Click “Save”
 
@@ -312,9 +312,9 @@ please follow the instructions below.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
 
-      Verifying Integration instructions <../verify>
+    Verifying Integration instructions <../verify>
 
 .. _integration/ecommerce_platforms/shopify/manual_integration_theme_migration:
 
@@ -337,7 +337,7 @@ you need to do the following:
 
           .. code-block:: html
 
-             <div id="talkable-offer"></div>
+            <div id="talkable-offer"></div>
 
           If there were any customizations in the `templates/page.talkable.liquid`, add them as well
 
@@ -352,15 +352,15 @@ you need to do the following:
         * Change the type of the main section to `talkable-campaign`
 
           .. image:: /_static/img/shopify/editor_template.png
-             :alt: Shopify editor - Talkable page section
-             :class: is-minimal
+            :alt: Shopify editor - Talkable page section
+            :class: is-minimal
 
           .. important::
-             The name of the section should be the same as the one you used
-             in the previous step when naming your section file.
+            The name of the section should be the same as the one you used
+            in the previous step when naming your section file.
 
           .. important::
-             If your main section is disabled, remove the row that does it.
+            If your main section is disabled, remove the row that does it.
 
 2. Dashboard page migration:
 
@@ -375,13 +375,13 @@ you need to do the following:
 
           .. code-block:: html
 
-             {% if shop.customer_accounts_enabled %}
-               {% if customer %}
-                 <div id="talkable-offer"></div>
-               {% else %}
-                 {{ 'Log in' | customer_login_link }}
-               {% endif %}
-             {% endif %}
+            {% if shop.customer_accounts_enabled %}
+              {% if customer %}
+                <div id="talkable-offer"></div>
+              {% else %}
+                {{ 'Log in' | customer_login_link }}
+              {% endif %}
+            {% endif %}
 
           If there were any customizations in the `templates/page.talkable-dashboard.liquid`, add them as well
 
@@ -397,20 +397,20 @@ you need to do the following:
 
           .. code-block:: JSON
 
-             {
-               "sections": {
-                 "main": {
-                   "type": "talkable-dashboard"
-                 }
-               }
-             }
+            {
+              "sections": {
+                "main": {
+                  "type": "talkable-dashboard"
+                }
+              }
+            }
 
           .. important::
-             The name of the section should be the same as the one you used
-             in the previous step when naming your section file.
+            The name of the section should be the same as the one you used
+            in the previous step when naming your section file.
 
           .. important::
-             If your main section is disabled, remove the row that does it.
+            If your main section is disabled, remove the row that does it.
 
 **Contact us**
 
diff --git a/source/integration/loyalty.rst b/source/integration/loyalty.rst
index f1ea715e4..52fb97d25 100644
--- a/source/integration/loyalty.rst
+++ b/source/integration/loyalty.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: You can integrate Talkable Loyalty to e-commerce sites in a few quick steps.
+  :description: You can integrate Talkable Loyalty to e-commerce sites in a few quick steps.
 
 Loyalty Integration (beta)
 ==========================
@@ -12,7 +12,7 @@ a few quick steps by adding the below scripts to your site.
 
 .. raw:: html
 
-   <h2>Integration</h2>
+  <h2>Integration</h2>
 
 1. Initialize Talkable integration library.
 
@@ -21,7 +21,7 @@ a few quick steps by adding the below scripts to your site.
 
  .. note::
 
-    Skip this step if you already have Talkable integrated on your site
+   Skip this step if you already have Talkable integrated on your site
 
 2. Add Loyalty Dashboard.
 
@@ -32,7 +32,7 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-      <div id="talkable-loyalty"></div>
+     <div id="talkable-loyalty"></div>
 
 3. Add Redeem Widget.
 
@@ -41,12 +41,12 @@ a few quick steps by adding the below scripts to your site.
 
    .. code-block:: html
 
-      <div id="talkable-loyalty"></div>
+     <div id="talkable-loyalty"></div>
 
    It is recommended to add it above the discount field. Examples:
 
    .. figure:: /_static/img/loyalty/loyalty_checkout.png
-      :alt: Sample checkout
+     :alt: Sample checkout
 
 4. Define Loyalty points redemption batches.
 
@@ -59,16 +59,16 @@ a few quick steps by adding the below scripts to your site.
    It is recommended to upload 100,000 single-use coupons into every coupon list.
 
    .. figure:: /_static/img/loyalty/redemption_batches.png
-      :alt: Redemption batches
+     :alt: Redemption batches
 
  .. note::
 
-    All design and loyalty campaign setup is done inside the Talkable platform,
-    then via iframe loyalty campaign content is injected into the site.
+   All design and loyalty campaign setup is done inside the Talkable platform,
+   then via iframe loyalty campaign content is injected into the site.
 
 .. raw:: html
 
-   <h2>Requirements</h2>
+  <h2>Requirements</h2>
 
 1. User accounts. The website must support user accounts since the loyalty program is only available to logged in users.
 
@@ -82,7 +82,7 @@ a few quick steps by adding the below scripts to your site.
 
  .. toctree::
 
-    loyalty/integration_components
-    loyalty/custom_app
-    loyalty/auto_enrollment
-    loyalty/shopify_integration
+   loyalty/integration_components
+   loyalty/custom_app
+   loyalty/auto_enrollment
+   loyalty/shopify_integration
diff --git a/source/integration/loyalty/auto_enrollment.rst b/source/integration/loyalty/auto_enrollment.rst
index b7f1d22d6..811393551 100644
--- a/source/integration/loyalty/auto_enrollment.rst
+++ b/source/integration/loyalty/auto_enrollment.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Find out how to auto-enroll loyalty members.
+  :description: Find out how to auto-enroll loyalty members.
 
 Auto-Enrollment
 ===============
@@ -34,7 +34,7 @@ For example, this could be used for enrolling users during registration or login
 Don't forget to include a consent checkbox that would inform your user that they are about to join the loyalty program.
 
 .. note::
-   `join_loyalty` is available since integration version 4.5.9.
+  `join_loyalty` is available since integration version 4.5.9.
 
 Code Example #1:
 ----------------
@@ -44,19 +44,19 @@ Use `authenticate_customer` to store current user data.
 When you call `join_loyalty`, you can pass empty object since Talkable will have access to the data from `authenticate_customer`.
 
 .. tip::
-   `authenticate_customer` data can also be reused by other integration functions.
+  `authenticate_customer` data can also be reused by other integration functions.
 
 .. code-block:: js
 
-   window._talkableq.push(["authenticate_customer", {
-     email: "loyalty@talkable.com", // required for `join_loyalty`
-     phone_number: '+12025551111',
-     first_name: "John",
-     last_name: "Smith",
-     custom_properties: {},
-     customer_id: "11111"
-   }]);
-   window._talkableq.push("join_loyalty", {})
+  window._talkableq.push(["authenticate_customer", {
+    email: "loyalty@talkable.com", // required for `join_loyalty`
+    phone_number: '+12025551111',
+    first_name: "John",
+    last_name: "Smith",
+    custom_properties: {},
+    customer_id: "11111"
+  }]);
+  window._talkableq.push("join_loyalty", {})
 
 Code Example #2:
 ----------------
@@ -64,15 +64,15 @@ Code Example #2:
 Pass loyalty member data directly to `join_loyalty`.
 
 .. note::
-   Arguments passed with `join_loyalty` override respective arguments from `authenticate_customer`.
+  Arguments passed with `join_loyalty` override respective arguments from `authenticate_customer`.
 
 .. code-block:: js
 
-   window._talkableq.push(["join_loyalty", {
-     email: "loyalty@talkable.com", // required
-     phone_number: '+12025551111',
-     first_name: "John",
-     last_name: "Smith",
-     custom_properties: {},
-     customer_id: "11111"
-   }]);
+  window._talkableq.push(["join_loyalty", {
+    email: "loyalty@talkable.com", // required
+    phone_number: '+12025551111',
+    first_name: "John",
+    last_name: "Smith",
+    custom_properties: {},
+    customer_id: "11111"
+  }]);
diff --git a/source/integration/loyalty/custom_app.rst b/source/integration/loyalty/custom_app.rst
index 913d7cda1..2331eb4ae 100644
--- a/source/integration/loyalty/custom_app.rst
+++ b/source/integration/loyalty/custom_app.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Learn how to use Custom app to receive data about loyalty events.
+  :description: Learn how to use Custom app to receive data about loyalty events.
 
 Custom App for Loyalty
 ======================
@@ -46,7 +46,7 @@ To determine which loyalty action triggered the Custom App, use `{{ action.ident
 `{{ action.rule }}` contains details about the action configuration that is responsible for a particular points collection.
 
 .. note::
-   `{{ action.rule }}` is optional for *"manual_adjustment"* actions and always blank for *"redeem"* actions.
+  `{{ action.rule }}` is optional for *"manual_adjustment"* actions and always blank for *"redeem"* actions.
 
 To see the full list of available variables, click "Show available variables" on the Custom App action configuration page.
 
diff --git a/source/integration/loyalty/integration_components.rst b/source/integration/loyalty/integration_components.rst
index 1a31cecfe..e409b797a 100644
--- a/source/integration/loyalty/integration_components.rst
+++ b/source/integration/loyalty/integration_components.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Find the components of what Talkable is composed.
+  :description: Find the components of what Talkable is composed.
 
 Integration Components
 ======================
@@ -44,19 +44,19 @@ script.
 
 .. code-block:: html
 
-   <!-- Begin Talkable integration code -->
-   <script async src="https://d2jjzw81hqbuqv.cloudfront.net/integration/clients/<YOUR-TALKABLE-SITE-ID>.min.js"></script>
-   <script>
-     window._talkableq = window._talkableq || [];
-     window._talkableq.unshift(['init', { site_id: '<YOUR-TALKABLE-SITE-ID>' }]);
+  <!-- Begin Talkable integration code -->
+  <script async src="https://d2jjzw81hqbuqv.cloudfront.net/integration/clients/<YOUR-TALKABLE-SITE-ID>.min.js"></script>
+  <script>
+    window._talkableq = window._talkableq || [];
+    window._talkableq.unshift(['init', { site_id: '<YOUR-TALKABLE-SITE-ID>' }]);
 
-     window._talkableq.push(['authenticate_customer', {
-       email: '', // required, loyalty program is only available to logged in users. Example: 'customer@example.com'
-       phone_number: '' // Optional, pass when available. Example: '+12025551111'
-       customer_id: '11111' // Optional, Customer ID inside your system
-     }]);
-   </script>
-   <!-- End Talkable integration code -->
+    window._talkableq.push(['authenticate_customer', {
+      email: '', // required, loyalty program is only available to logged in users. Example: 'customer@example.com'
+      phone_number: '' // Optional, pass when available. Example: '+12025551111'
+      customer_id: '11111' // Optional, Customer ID inside your system
+    }]);
+  </script>
+  <!-- End Talkable integration code -->
 
 Initialization Script Notes
 ---------------------------
@@ -66,7 +66,7 @@ Initialization Script Notes
    here:
 
    .. figure:: /_static/img/site_id.png
-      :alt: Site ID
+     :alt: Site ID
 
 2. **Variables.** Use your dynamic variables to pass user details.
 
@@ -81,13 +81,13 @@ Add the following Talkable Container DIV in the body of every page where you wan
 
 .. code-block:: html
 
-   <div id="talkable-loyalty"></div>
+  <div id="talkable-loyalty"></div>
 
 The `Talkable Initialization Script <Initialization Script_>`_ must be present in your head template in order for the Loyalty Dashboard to work. The placement of the DIV tag is important since it's going to determine where the campaign will be rendered.
 
 .. note::
-   The same DIV tag is used for both Loyalty Dashboard and Loyalty Redeem Widget.
-   You can find more info about where to place the DIV tag in :ref:`Loyalty Dashboard Placement <campaigns/campaign_placements/loyalty_dashboard>` and :ref:`Loyalty Widget Placement <campaigns/campaign_placements/loyalty_widget>`.
+  The same DIV tag is used for both Loyalty Dashboard and Loyalty Redeem Widget.
+  You can find more info about where to place the DIV tag in :ref:`Loyalty Dashboard Placement <campaigns/campaign_placements/loyalty_dashboard>` and :ref:`Loyalty Widget Placement <campaigns/campaign_placements/loyalty_widget>`.
 
 Loyalty Dashboard Notes
 -----------------------
@@ -111,12 +111,12 @@ use the following code:
 
 .. code-block:: html
 
-   <script>
-     window._talkableq.push(['register_loyalty_action', {
-       rule_identifier: '', // required, can be found in Campaign Rules -> Loyalty action configurations -> "identifier" field
-       traffic_source: '' // optional
-     }]);
-   </script>
+  <script>
+    window._talkableq.push(['register_loyalty_action', {
+      rule_identifier: '', // required, can be found in Campaign Rules -> Loyalty action configurations -> "identifier" field
+      traffic_source: '' // optional
+    }]);
+  </script>
 
 Loyalty Actions Notes
 ---------------------
diff --git a/source/integration/loyalty/shopify_integration.rst b/source/integration/loyalty/shopify_integration.rst
index c09b1f81d..d23c4f523 100644
--- a/source/integration/loyalty/shopify_integration.rst
+++ b/source/integration/loyalty/shopify_integration.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Learn how to manually set up loyalty Shopify integration.
+  :description: Learn how to manually set up loyalty Shopify integration.
 
 Shopify Integration
 ===================
@@ -38,9 +38,9 @@ Manual integration
 
           .. code-block:: html
 
-             {% if shop.customer_accounts_enabled %}
-               <div id="talkable-loyalty"></div>
-             {% endif %}
+            {% if shop.customer_accounts_enabled %}
+              <div id="talkable-loyalty"></div>
+            {% endif %}
 
         * Optionally, update the schema name to anything meaningful, for example, “Loyalty dashboard“
         * Click “Save”
@@ -54,20 +54,20 @@ Manual integration
 
           .. code-block:: JSON
 
-             {
-               "sections": {
-                 "main": {
-                   "type": "talkable-loyalty-dashboard"
-                 }
-               }
-             }
+            {
+              "sections": {
+                "main": {
+                  "type": "talkable-loyalty-dashboard"
+                }
+              }
+            }
 
           .. important::
-             The name of the section should be the same as the one you used
-             in the previous step when naming your section file.
+            The name of the section should be the same as the one you used
+            in the previous step when naming your section file.
 
           .. important::
-             If your main section is disabled, remove the row that does it.
+            If your main section is disabled, remove the row that does it.
 
     3. Create a page:
 
@@ -80,7 +80,7 @@ Manual integration
 
 .. raw:: html
 
-   <h2>Requirements</h2>
+  <h2>Requirements</h2>
 
 User accounts. The website must support user accounts since the loyalty program is only available to logged in users.
 
@@ -103,9 +103,9 @@ you need to do the following:
 
       .. code-block:: html
 
-         {% if shop.customer_accounts_enabled %}
-           <div id="talkable-loyalty"></div>
-         {% endif %}
+        {% if shop.customer_accounts_enabled %}
+          <div id="talkable-loyalty"></div>
+        {% endif %}
 
       If there were any customizations in the `templates/page.talkable-loyalty-dashboard.liquid`, add them as well
 
@@ -121,17 +121,17 @@ you need to do the following:
 
       .. code-block:: JSON
 
-         {
-           "sections": {
-             "main": {
-               "type": "talkable-loyalty-dashboard"
-             }
-           }
-         }
+        {
+          "sections": {
+            "main": {
+              "type": "talkable-loyalty-dashboard"
+            }
+          }
+        }
 
       .. important::
-         The name of the section should be the same as the one you used
-         in the previous step when naming your section file.
+        The name of the section should be the same as the one you used
+        in the previous step when naming your section file.
 
       .. important::
-         If your main section is disabled, remove the row that does it.
+        If your main section is disabled, remove the row that does it.
diff --git a/source/integration/verify.rst b/source/integration/verify.rst
index b648ac1c6..25a5bc8de 100644
--- a/source/integration/verify.rst
+++ b/source/integration/verify.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: After installing Talkable, you should verify that the integration is working.
+  :description: After installing Talkable, you should verify that the integration is working.
 
 Verifying Integration
 =====================
diff --git a/source/ios_sdk.rst b/source/ios_sdk.rst
index 2b2044681..082b9f932 100644
--- a/source/ios_sdk.rst
+++ b/source/ios_sdk.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Talkable has an iOS framework enabling you to use Talkable in iOS apps
+  :description: Talkable has an iOS framework enabling you to use Talkable in iOS apps
 
 Talkable iOS SDK
 ################
@@ -24,10 +24,10 @@ Contents:
 
 .. toctree::
 
-   ios_sdk/getting_started
-   ios_sdk/integration
-   ios_sdk/social_sharing
-   ios_sdk/api_integration
-   ios_sdk/advanced
-   ios_sdk/custom_deep_linking
-   ios_sdk/example
+  ios_sdk/getting_started
+  ios_sdk/integration
+  ios_sdk/social_sharing
+  ios_sdk/api_integration
+  ios_sdk/advanced
+  ios_sdk/custom_deep_linking
+  ios_sdk/example
diff --git a/source/ios_sdk/advanced.rst b/source/ios_sdk/advanced.rst
index 5ec35562b..1ae3a7228 100644
--- a/source/ios_sdk/advanced.rst
+++ b/source/ios_sdk/advanced.rst
@@ -72,13 +72,13 @@ Implement TalkableDelegate
 
    .. code-block:: objc
 
-      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
-      - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
-      - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+     - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
+     - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+     - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
    .. note::
 
-      See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
+     See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
 .. _ios_sdk/advanced/notifications:
 
@@ -151,4 +151,4 @@ See all debugging information in your console which can help you to understand w
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/ios_sdk/api_integration.rst b/source/ios_sdk/api_integration.rst
index a810d8604..066fe9456 100644
--- a/source/ios_sdk/api_integration.rst
+++ b/source/ios_sdk/api_integration.rst
@@ -78,28 +78,28 @@ via |api_v2_share_via_social_channel|.
 
 .. code-block:: objc
 
-   MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
-   delegate.shortUrlCode = shortUrlCode;
-   FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
-   content.contentURL = [NSURL URLWithString:[params objectForKey:[claimLinks objectForKey:TKBLShareChannelFacebook]]];
-   [FBSDKShareDialog showFromViewController:self
-                                withContent:content
-                                   delegate:delegate];
+  MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
+  delegate.shortUrlCode = shortUrlCode;
+  FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
+  content.contentURL = [NSURL URLWithString:[params objectForKey:[claimLinks objectForKey:TKBLShareChannelFacebook]]];
+  [FBSDKShareDialog showFromViewController:self
+                               withContent:content
+                                  delegate:delegate];
 
-   // ...
+  // ...
 
-   @implementation MyFBSDKDelegateClass
+  @implementation MyFBSDKDelegateClass
 
-   @synthesize shortUrlCode;
+  @synthesize shortUrlCode;
 
-   - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
-    if (_shortUrlCode != nil)
-       [[Talkable manager] createSocialShare:_shortUrlCode
-                                     channel:TKBLShareChannelFacebook
-                                 withHandler:^(NSDictionary* response, NSError* error) {...}];
-   }
+  - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
+   if (_shortUrlCode != nil)
+      [[Talkable manager] createSocialShare:_shortUrlCode
+                                    channel:TKBLShareChannelFacebook
+                                withHandler:^(NSDictionary* response, NSError* error) {...}];
+  }
 
-   @end
+  @end
 
 .. raw:: html
 
@@ -107,15 +107,15 @@ via |api_v2_share_via_social_channel|.
 
 .. code-block:: objc
 
-   TWTRComposer *composer = [[TWTRComposer alloc] init];
-   [composer setText:[params objectForKey:TKBLShareMessage]];
-   [composer showFromViewController:self completion:^(TWTRComposerResult result) {
-     if (result == TWTRComposerResultDone) {
-       [[Talkable manager] createSocialShare:shortUrlCode
-                                     channel:TKBLShareChannelTwitter
-                                 withHandler:^(NSDictionary* response, NSError* error) {...}];
-     }
-   }];
+  TWTRComposer *composer = [[TWTRComposer alloc] init];
+  [composer setText:[params objectForKey:TKBLShareMessage]];
+  [composer showFromViewController:self completion:^(TWTRComposerResult result) {
+    if (result == TWTRComposerResultDone) {
+      [[Talkable manager] createSocialShare:shortUrlCode
+                                    channel:TKBLShareChannelTwitter
+                                withHandler:^(NSDictionary* response, NSError* error) {...}];
+    }
+  }];
 
 .. note::
 
@@ -141,9 +141,9 @@ Legacy social sharing
 
    .. warning::
 
-      Starting with v1.4.9, this method is deprecated and offers only limited Facebook sharing support.
-      Native sharing or custom implementation based on Facebook/Twitter SDK should be used instead.
-      See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
+     Starting with v1.4.9, this method is deprecated and offers only limited Facebook sharing support.
+     Native sharing or custom implementation based on Facebook/Twitter SDK should be used instead.
+     See :ref:`Social Sharing <ios_sdk/social_sharing>` for details.
 
 
 Email Share
@@ -196,4 +196,4 @@ to fetch the Offer.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/ios_sdk/custom_deep_linking.rst b/source/ios_sdk/custom_deep_linking.rst
index e53167dac..38b73c0fc 100644
--- a/source/ios_sdk/custom_deep_linking.rst
+++ b/source/ios_sdk/custom_deep_linking.rst
@@ -17,12 +17,12 @@ To use deep linking with Talkable campaigns, simply use your deep link URL as yo
 
 .. note::
 
-    If you have configured a custom Friend Destination URL for your campaign, make sure the following GET parameters
-    are present in the final URL: ``?tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}``.
+  If you have configured a custom Friend Destination URL for your campaign, make sure the following GET parameters
+  are present in the final URL: ``?tkbl_cvuuid={{ visitor_uuid }}&talkable_visitor_offer_id={{ friend_offer.id }}``.
 
-    All major deep linking providers support passing additional GET parameters with the deep link.
-    This functionality is used to pass the Friend's identifying information to the Talkable SDK in your iOS app.
-    To use this functionality with Firebase, refer to this document: `Manually constructing a Dynamic Link URL`_.
+  All major deep linking providers support passing additional GET parameters with the deep link.
+  This functionality is used to pass the Friend's identifying information to the Talkable SDK in your iOS app.
+  To use this functionality with Firebase, refer to this document: `Manually constructing a Dynamic Link URL`_.
 
 2. Pass deep linking params to the Talkable SDK
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -34,40 +34,40 @@ Use ``handleURLParams:`` method if you have a ``NSDictionary`` with params passe
 
 .. code-block:: objc
 
-    // For Branch.io
+  // For Branch.io
 
-    [[Branch getInstance] initSessionWithLaunchOptions:launchOptions andRegisterDeepLinkHandler:^(NSDictionary *params, NSError *error) {
+  [[Branch getInstance] initSessionWithLaunchOptions:launchOptions andRegisterDeepLinkHandler:^(NSDictionary *params, NSError *error) {
         [[Talkable manager] handleURLParams:params];
-    }];
+  }];
 
 .. note::
 
-    Most deep linking services provide additional parameters in the deep link handler to indicate whether the app was installed
-    on this device for the first time, reinstalled or simply launched. You can use these params to register installs
-    only when desired conditions are met.
+  Most deep linking services provide additional parameters in the deep link handler to indicate whether the app was installed
+  on this device for the first time, reinstalled or simply launched. You can use these params to register installs
+  only when desired conditions are met.
 
 .. code-block:: objc
 
-    // For GetSocial
+  // For GetSocial
 
-    [GetSocial referralDataWithSuccess:^(GetSocialReferralData * _Nullable referralData) {
-        if ([referralData isFirstMatch]) {
-            [[Talkable manager] handleURLParams:[referralData linkParams]];
-        }
-    } failure:^(NSError * _Nonnull error) {}];
+  [GetSocial referralDataWithSuccess:^(GetSocialReferralData * _Nullable referralData) {
+      if ([referralData isFirstMatch]) {
+          [[Talkable manager] handleURLParams:[referralData linkParams]];
+      }
+  } failure:^(NSError * _Nonnull error) {}];
 
 Use ``handleOpenURL:`` method if you handle deep link as ``NSURL`` using the standard
 ``application:openURL:options:`` method (Firebase).
 
 .. code-block:: objc
 
-    // For Firebase
+  // For Firebase
 
-    - (BOOL)application:(UIApplication *)app
-                openURL:(NSURL *)url
-                options:(NSDictionary<NSString *, id> *)options {
-                    [[Talkable manager] handleOpenURL:url];
-                }
+  - (BOOL)application:(UIApplication *)app
+              openURL:(NSURL *)url
+              options:(NSDictionary<NSString *, id> *)options {
+                  [[Talkable manager] handleOpenURL:url];
+              }
 
 Calling either of these methods will register the app installation event in Talkable and complete the referral cycle.
 You can then use the :ref:`retrieveRewardsWithHandler: <ios_sdk/api_integration>` method to check for rewards or subscribe
diff --git a/source/ios_sdk/example.rst b/source/ios_sdk/example.rst
index 243dec7b8..11066c729 100644
--- a/source/ios_sdk/example.rst
+++ b/source/ios_sdk/example.rst
@@ -12,4 +12,4 @@ If you have any questions, don’t hesitate to email us at support@talkable.com.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/ios_sdk/getting_started.rst b/source/ios_sdk/getting_started.rst
index c244f997a..9bd51c546 100644
--- a/source/ios_sdk/getting_started.rst
+++ b/source/ios_sdk/getting_started.rst
@@ -36,9 +36,9 @@ Alternatively, you can add Talkable SDK directly to a `Package.swift` manifest:
 
   .. code-block:: swift
 
-      dependencies: [
-          .package(url: "https://github.com/talkable/ios-sdk.git", .upToNextMajor(from: "1.5.1"))
-      ]
+    dependencies: [
+        .package(url: "https://github.com/talkable/ios-sdk.git", .upToNextMajor(from: "1.5.1"))
+    ]
 
 CocoaPods
 `````````
diff --git a/source/ios_sdk/integration.rst b/source/ios_sdk/integration.rst
index 0e00a370b..a3f029929 100644
--- a/source/ios_sdk/integration.rst
+++ b/source/ios_sdk/integration.rst
@@ -12,8 +12,8 @@ The SDK is installed and configured. Now you can integrate Standalone and/or Pos
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
 
-      Standalone Campaign <integration/standalone>
-      Post Purchase Campaign <integration/post_purchase>
-      Custom Events <integration/event>
+    Standalone Campaign <integration/standalone>
+    Post Purchase Campaign <integration/post_purchase>
+    Custom Events <integration/event>
diff --git a/source/ios_sdk/integration/post_purchase.rst b/source/ios_sdk/integration/post_purchase.rst
index 41376cc2c..377a9b15b 100644
--- a/source/ios_sdk/integration/post_purchase.rst
+++ b/source/ios_sdk/integration/post_purchase.rst
@@ -12,27 +12,27 @@ Here is an example of a Purchase capturing, this action should be triggered on t
 
 .. code-block:: objc
 
-   #import <TalkableSDK/Talkable.h>
-   // ...
-   NSDictionary* params = @{
-     TKBLPurchaseKey: @{
-       TKBLPurchaseOrderNumberKey: @"100130", // REQUIRED - Order number
-       TKBLPurchaseEmailKey: @"customer@example.com", // REQUIRED - Customer Email
-       TKBLPurchaseSubtotalKey: [NSNumber numberWithDouble:22.33], // REQUIRED - Purchase Subtotal
-       TKBLPurchaseCouponCodeKey: @"TEST25", // REQUIRED - Coupon code used at checkout, pass multiple as an array: @[@"SAVE20", @"FREE-SHIPPING"]. Pass @"" if there is no coupon code.
-       TKBLPurchaseOrderItemsKey:@[
-         @{
-           TKBLPurchaseOrderItemProductIDKey: @"sku3", // Item Product ID
-           TKBLPurchaseOrderItemPriceKey: [NSNumber numberWithDouble:4.99], // Item Unit Price
-           TKBLPurchaseOrderItemQuantityKey: [NSNumber numberWithUnsignedInt:5], // Item Quantity
-           TKBLPurchaseOrderItemTitleKey: @"Amazing Product 3", // Name of the product
-           TKBLPurchaseOrderItemUrlKey: @"http://www.store.com/product2", // URL of the product page
-           TKBLPurchaseOrderItemImageUrlKey: @"http://www.store.com/product2/image.jpg" // URL of the product image
-         }
-       ]
-     }
-   };
-   [[Talkable manager] registerOrigin:TKBLPurchase params:params];
+  #import <TalkableSDK/Talkable.h>
+  // ...
+  NSDictionary* params = @{
+    TKBLPurchaseKey: @{
+      TKBLPurchaseOrderNumberKey: @"100130", // REQUIRED - Order number
+      TKBLPurchaseEmailKey: @"customer@example.com", // REQUIRED - Customer Email
+      TKBLPurchaseSubtotalKey: [NSNumber numberWithDouble:22.33], // REQUIRED - Purchase Subtotal
+      TKBLPurchaseCouponCodeKey: @"TEST25", // REQUIRED - Coupon code used at checkout, pass multiple as an array: @[@"SAVE20", @"FREE-SHIPPING"]. Pass @"" if there is no coupon code.
+      TKBLPurchaseOrderItemsKey:@[
+        @{
+          TKBLPurchaseOrderItemProductIDKey: @"sku3", // Item Product ID
+          TKBLPurchaseOrderItemPriceKey: [NSNumber numberWithDouble:4.99], // Item Unit Price
+          TKBLPurchaseOrderItemQuantityKey: [NSNumber numberWithUnsignedInt:5], // Item Quantity
+          TKBLPurchaseOrderItemTitleKey: @"Amazing Product 3", // Name of the product
+          TKBLPurchaseOrderItemUrlKey: @"http://www.store.com/product2", // URL of the product page
+          TKBLPurchaseOrderItemImageUrlKey: @"http://www.store.com/product2/image.jpg" // URL of the product image
+        }
+      ]
+    }
+  };
+  [[Talkable manager] registerOrigin:TKBLPurchase params:params];
 
 .. note::
 
@@ -42,4 +42,4 @@ Here is an example of a Purchase capturing, this action should be triggered on t
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/ios_sdk/integration/standalone.rst b/source/ios_sdk/integration/standalone.rst
index 74ccce780..417f1b373 100644
--- a/source/ios_sdk/integration/standalone.rst
+++ b/source/ios_sdk/integration/standalone.rst
@@ -40,4 +40,4 @@ Note that `params` are empty, in this case user will see Signup form on :ref:`Ad
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/ios_sdk/social_sharing.rst b/source/ios_sdk/social_sharing.rst
index 818abddc0..09f3ca2a5 100644
--- a/source/ios_sdk/social_sharing.rst
+++ b/source/ios_sdk/social_sharing.rst
@@ -27,7 +27,7 @@ showFacebookShareDialogWithParams:delegate:
 
 .. code-block:: objc
 
-   - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
+  - (void)showFacebookShareDialogWithParams:(NSDictionary*)params delegate:(id)delegate;
 
 This method is called when the user clicks on the 'Facebook Share' button.
 The ``params`` dictionary contains information on the content being shared and will have the following keys:
@@ -45,13 +45,13 @@ Example
 
 .. code-block:: objc
 
-   - (void)showFacebookShareDialogWithParams:(NSDictionary *)params delegate:(id)delegate {
-        FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
-        content.contentURL = [NSURL URLWithString:[params objectForKey:TKBLOfferClaimUrlKey]];
-        [FBSDKShareDialog showFromViewController:self
-                                     withContent:content
-                                        delegate:delegate];
-    }
+  - (void)showFacebookShareDialogWithParams:(NSDictionary *)params delegate:(id)delegate {
+       FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
+       content.contentURL = [NSURL URLWithString:[params objectForKey:TKBLOfferClaimUrlKey]];
+       [FBSDKShareDialog showFromViewController:self
+                                    withContent:content
+                                       delegate:delegate];
+   }
 
 
 showFacebookShareDialogWithParams:completionHandler:
@@ -59,7 +59,7 @@ showFacebookShareDialogWithParams:completionHandler:
 
 .. code-block:: objc
 
-   - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+  - (void)showFacebookShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
 This method is also called when the user clicks on the 'Facebook Share' button, but instead of ``delegate`` param it
 provides the ``completionHandler`` block that should be called when sharing is completed successfully. Use
@@ -72,28 +72,28 @@ Example
 
 .. code-block:: objc
 
-   - (void)showFacebookShareDialogWithParams:(NSDictionary *)params completion:(void (^)())completionHandler {
-       MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
-       delegate.talkableCompletionHandler = completionHandler;
-       FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
-       content.contentURL = [NSURL URLWithString:[params objectForKey:TKBLOfferClaimUrlKey]];
-       [FBSDKShareDialog showFromViewController:self
-                                    withContent:content
-                                       delegate:delegate];
-   }
+  - (void)showFacebookShareDialogWithParams:(NSDictionary *)params completion:(void (^)())completionHandler {
+      MyFBSDKDelegateClass* delegate = [self myFBSDKDelegate];
+      delegate.talkableCompletionHandler = completionHandler;
+      FBSDKShareLinkContent *content = [[FBSDKShareLinkContent alloc] init];
+      content.contentURL = [NSURL URLWithString:[params objectForKey:TKBLOfferClaimUrlKey]];
+      [FBSDKShareDialog showFromViewController:self
+                                   withContent:content
+                                      delegate:delegate];
+  }
 
-   // ...
+  // ...
 
-   @implementation MyFBSDKDelegateClass
+  @implementation MyFBSDKDelegateClass
 
-   @synthesize talkableCompletionHandler;
+  @synthesize talkableCompletionHandler;
 
-   - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
-    if ((_talkableCompletionHandler) != nil)
-      _talkableCompletionHandler();
-   }
+  - (void)sharer:(id)sharer didCompleteWithResults:(NSDictionary<NSString *, id> *)results {
+   if ((_talkableCompletionHandler) != nil)
+     _talkableCompletionHandler();
+  }
 
-   @end
+  @end
 
 
 showTwitterShareDialogWithParams:completionHandler:
@@ -101,7 +101,7 @@ showTwitterShareDialogWithParams:completionHandler:
 
 .. code-block:: objc
 
-   - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
+  - (void)showTwitterShareDialogWithParams:(NSDictionary*)params completion:(void (^)())completionHandler;
 
 This method is called when the user clicks on the Twitter Share button. The ``params`` and ``completionHandler``
 attributes are analogous to the previous method.
@@ -111,17 +111,17 @@ Example
 
 .. code-block:: objc
 
-   - (void)showTwitterShareDialogWithParams:(NSDictionary *)params completion:(void (^)())completionHandler {
-      TWTRComposer *composer = [[TWTRComposer alloc] init];
+  - (void)showTwitterShareDialogWithParams:(NSDictionary *)params completion:(void (^)())completionHandler {
+     TWTRComposer *composer = [[TWTRComposer alloc] init];
 
-      [composer setText:[params objectForKey:TKBLShareMessage]];
+     [composer setText:[params objectForKey:TKBLShareMessage]];
 
-      [composer showFromViewController:self completion:^(TWTRComposerResult result) {
-          if (result == TWTRComposerResultDone) {
-               completionHandler();
-          }
-      }];
-   }
+     [composer showFromViewController:self completion:^(TWTRComposerResult result) {
+         if (result == TWTRComposerResultDone) {
+              completionHandler();
+         }
+     }];
+  }
 
 Legacy Sharing using Social.framework
 -------------------------------------
@@ -141,10 +141,10 @@ to ensure a seamless transition to new implementations.
 
 .. note::
 
-   Talkable iOS SDK v1.4.9 features improved support of legacy Facebook sharing via Social.framework. If you are having trouble
-   with your current implementation, please upgrade to the latest version. Note that we can only try to provide the best
-   transitioning experience, and this fallback should not be regarded as a permanent solution. We encourage developers to switch
-   to delegate methods for social sharing.
+  Talkable iOS SDK v1.4.9 features improved support of legacy Facebook sharing via Social.framework. If you are having trouble
+  with your current implementation, please upgrade to the latest version. Note that we can only try to provide the best
+  transitioning experience, and this fallback should not be regarded as a permanent solution. We encourage developers to switch
+  to delegate methods for social sharing.
 
 Social Sharing from a native campaign
 -------------------------------------
diff --git a/source/partials/common.rst b/source/partials/common.rst
index fab3e4ca1..f6252c14a 100644
--- a/source/partials/common.rst
+++ b/source/partials/common.rst
@@ -1,90 +1,90 @@
 .. |nbsp| raw:: html
 
-   &nbsp;
+  &nbsp;
 
 .. |space_indent| raw:: html
 
-   <span class="inline mll"></span>
+  <span class="inline mll"></span>
 
 .. |br| raw:: html
 
-   <br>
+  <br>
 
 .. |hr| raw:: html
 
-   <hr>
+  <hr>
 
 .. role:: underline
-   :class: underline
+  :class: underline
 
 .. |cta| raw:: html
 
-   <abbr title="Call to action">CTA</abbr>
+  <abbr title="Call to action">CTA</abbr>
 
 .. |advocate| raw:: html
 
-   <abbr title="Person who shares an offer with their Friend(s)">Advocate</abbr>
+  <abbr title="Person who shares an offer with their Friend(s)">Advocate</abbr>
 
 .. |friend| raw:: html
 
-   <abbr title="Person who is invited to participate in Campaign by Advocate">Friend</abbr>
+  <abbr title="Person who is invited to participate in Campaign by Advocate">Friend</abbr>
 
 .. |loyalty_member| raw:: html
 
-   <abbr title="Person who participates in the Loyalty program">Loyalty member</abbr>
+  <abbr title="Person who participates in the Loyalty program">Loyalty member</abbr>
 
 .. |origin| raw:: html
 
-   <abbr title="Origin is the point where a referral loop begins (Standalone or Post Purchase campaign)">Origin</abbr>
+  <abbr title="Origin is the point where a referral loop begins (Standalone or Post Purchase campaign)">Origin</abbr>
 
 .. |iso8601| raw:: html
 
-   <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601</a>
+  <a href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601</a>
 
 .. |iso3166| raw:: html
 
-   <a href="https://en.wikipedia.org/wiki/ISO_3166-2" target="_blank">ISO 3166-2</a>
+  <a href="https://en.wikipedia.org/wiki/ISO_3166-2" target="_blank">ISO 3166-2</a>
 
 .. |liquid| raw:: html
 
-   <a href="https://github.com/Shopify/liquid" target="_blank">Liquid</a>
+  <a href="https://github.com/Shopify/liquid" target="_blank">Liquid</a>
 
 .. |contact_us| raw:: html
 
-   <a href="https://www.talkable.com/contact" target="_blank">contact us</a>
+  <a href="https://www.talkable.com/contact" target="_blank">contact us</a>
 
 .. |api_v2_campaigns| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Campaigns" target="_blank">Campaigns API</a>
+  <a href="https://www.talkable.com/api-docs/#/Campaigns" target="_blank">Campaigns API</a>
 
 .. |api_v2_offer| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Advocate%20Offers/findAdvocateOffer" target="_blank">Offer</a>
+  <a href="https://www.talkable.com/api-docs/#/Advocate%20Offers/findAdvocateOffer" target="_blank">Offer</a>
 
 .. |api_v2_origin| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Origins/createOrigin" target="_blank">Origin</a>
+  <a href="https://www.talkable.com/api-docs/#/Origins/createOrigin" target="_blank">Origin</a>
 
 .. |api_v2_origins| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Origins/createOrigin" target="_blank">Origins API</a>
+  <a href="https://www.talkable.com/api-docs/#/Origins/createOrigin" target="_blank">Origins API</a>
 
 .. |api_v2_referrals| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Referrals/updateReferralStatus" target="_blank">Referrals API</a>
+  <a href="https://www.talkable.com/api-docs/#/Referrals/updateReferralStatus" target="_blank">Referrals API</a>
 
 .. |api_v2_reward| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Rewards" target="_blank">Reward</a>
+  <a href="https://www.talkable.com/api-docs/#/Rewards" target="_blank">Reward</a>
 
 .. |api_v2_share_via_email| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Shares/shareViaEmail" target="_blank">Shares API</a>
+  <a href="https://www.talkable.com/api-docs/#/Shares/shareViaEmail" target="_blank">Shares API</a>
 
 .. |api_v2_share_via_social_channel| raw:: html
 
-   <a href="https://www.talkable.com/api-docs/#/Shares/shareViaSocialChannel" target="_blank">Shares API</a>
+  <a href="https://www.talkable.com/api-docs/#/Shares/shareViaSocialChannel" target="_blank">Shares API</a>
 
 .. |page_break| raw:: html
 
-   <div class="page-break-after"></div>
+  <div class="page-break-after"></div>
diff --git a/source/partials/coupon_as_reward.rst b/source/partials/coupon_as_reward.rst
index f59c6f545..0f3cbaed8 100644
--- a/source/partials/coupon_as_reward.rst
+++ b/source/partials/coupon_as_reward.rst
@@ -1,13 +1,13 @@
 .. raw:: html
 
-   <h2>Coupon codes as a reward</h2>
+  <h2>Coupon codes as a reward</h2>
 
 .. important::
 
-   If referral campaigns are set-up to reward either Friends or Advocates with
-   Talkable provided coupon codes, then the Reward Webhook is called for
-   informational purposes only. It is a notification that the reward has been
-   provided. Note, Talkable gets these coupons either by manual upload from the
-   Dashboard, or if configured, Talkable will call the  :ref:`Create Coupon
-   Webhook <web_hooks/create_coupon>` to generate additional coupons
-   automatically.
+  If referral campaigns are set-up to reward either Friends or Advocates with
+  Talkable provided coupon codes, then the Reward Webhook is called for
+  informational purposes only. It is a notification that the reward has been
+  provided. Note, Talkable gets these coupons either by manual upload from the
+  Dashboard, or if configured, Talkable will call the  :ref:`Create Coupon
+  Webhook <web_hooks/create_coupon>` to generate additional coupons
+  automatically.
diff --git a/source/partials/developer_email_note.rst b/source/partials/developer_email_note.rst
index 1a1d38637..cd4e40890 100644
--- a/source/partials/developer_email_note.rst
+++ b/source/partials/developer_email_note.rst
@@ -1,5 +1,5 @@
 .. note::
 
-   Ideal email width is 480px. This is a most universal width for both
-   mobile and desktop platforms.
-   :ref:`Read more about email design <designer/email>`.
+  Ideal email width is 480px. This is a most universal width for both
+  mobile and desktop platforms.
+  :ref:`Read more about email design <designer/email>`.
diff --git a/source/partials/incentive_types.rst b/source/partials/incentive_types.rst
index a63050b9a..7e4aab583 100644
--- a/source/partials/incentive_types.rst
+++ b/source/partials/incentive_types.rst
@@ -1,6 +1,6 @@
 .. raw:: html
 
-   <h2>Incentive types</h2>
+  <h2>Incentive types</h2>
 
 Incentives can be of 3 following general types.
 
diff --git a/source/partials/note_sample_code.rst b/source/partials/note_sample_code.rst
index 90bcd3028..65fc30980 100644
--- a/source/partials/note_sample_code.rst
+++ b/source/partials/note_sample_code.rst
@@ -1,3 +1,3 @@
 .. note::
 
-   Replace **<YOUR-TALKABLE-SITE-ID>** with your Talkable Site ID which is displayed on the integration page.
+  Replace **<YOUR-TALKABLE-SITE-ID>** with your Talkable Site ID which is displayed on the integration page.
diff --git a/source/web_hooks.rst b/source/web_hooks.rst
index bb61e0793..df099b664 100644
--- a/source/web_hooks.rst
+++ b/source/web_hooks.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Webhooks are triggered by events on Talkable’s site.
+  :description: Webhooks are triggered by events on Talkable’s site.
 
 Webhooks
 ########
@@ -22,29 +22,29 @@ Each Webhook in Talkable is defined with an HTTP URL to deliver Webhook data
 
 .. raw:: html
 
-   <h2>Available Webhooks</h2>
+  <h2>Available Webhooks</h2>
 
 Below is a user experience flow showing when Talkable Webhooks are called.
 For more details concerning specific Talkable Webhooks, click the appropriate
 Webhook type in the left-hand menu.
 
 .. image:: /_static/img/flowchart_webhooks_1.png
-   :alt: Webhooks Flowchart
-   :class: is-minimal
+  :alt: Webhooks Flowchart
+  :class: is-minimal
 
 .. note::
 
-   The Reward Webhooks will only send if there is an associated incentive
-   configured. For example, for the 'Reward Webhook' (reason = signup) to send,
-   there must be a signup incentive configured in the campaign rules.
+  The Reward Webhooks will only send if there is an associated incentive
+  configured. For example, for the 'Reward Webhook' (reason = signup) to send,
+  there must be a signup incentive configured in the campaign rules.
 
 .. raw:: html
 
-   <h2>Set Up</h2>
+  <h2>Set Up</h2>
 
 .. image:: /_static/img/menu_webhooks_screenshot.png
-   :alt: Webhooks Menu Item
-   :class: is-minimal
+  :alt: Webhooks Menu Item
+  :class: is-minimal
 
 1. Set up and test Talkable Webhooks by navigating to **Menu** then **Webhooks**
 2. Proceed to **Create New Webhook**
@@ -61,7 +61,7 @@ by Webhook type.
 
 .. raw:: html
 
-   <h2>Testing</h2>
+  <h2>Testing</h2>
 
 Testing webhooks can be accomplished with the help of Webhook Tester, an external
 service that tests your post-receive messages.
@@ -78,7 +78,7 @@ service that tests your post-receive messages.
 
 .. raw:: html
 
-   <h2>Data</h2>
+  <h2>Data</h2>
 
 All Webhooks are delivered as an HTTP Post request with the main parameter
 called payload. All data inside this parameter is encoded as JSON. Below is
@@ -86,11 +86,11 @@ a PHP parameter decode example:
 
 .. code-block:: php
 
-   json_decode($_POST["payload"])
+  json_decode($_POST["payload"])
 
 .. raw:: html
 
-   <h2>Parsing Timestamps</h2>
+  <h2>Parsing Timestamps</h2>
 
 **Timestamp data type** is not a part of JSON standard. Timestamps
 are passed as strings in |iso8601| compatible format. To function properly, ensure
@@ -99,7 +99,7 @@ https://stackoverflow.com/questions/2201925/converting-iso-8601-compliant-string
 
 .. raw:: html
 
-   <h2>Response Codes</h2>
+  <h2>Response Codes</h2>
 
 Talkable considers a Webhook as "delivered successfully" when a site
 server returns a **2xx response status**. Otherwise Talkable will continually
@@ -107,7 +107,7 @@ retry to deliver a Webhook after a set interval of time.
 
 .. raw:: html
 
-   <h2>HTTP Responses and Their Meanings</h2>
+  <h2>HTTP Responses and Their Meanings</h2>
 
 * 2xx: Success
 * 200: OK
@@ -126,7 +126,7 @@ Talkable will retry delivery of Webhook if any other error code is received.
 
 .. raw:: html
 
-   <h2>Security Key</h2>
+  <h2>Security Key</h2>
 
 Talkable includes a ``key`` parameter in Webhooks which are unique to each site
 as a way to identify Talkable as an authorized server. Your Talkable Webhook
@@ -134,7 +134,7 @@ security key can be found in the Webhook set up page.
 
 .. raw:: html
 
-   <h2>Type</h2>
+  <h2>Type</h2>
 
 The ``type`` parameter of a Webhook request can be used to identify which Webhook
 is received without looking at the payload. This will be useful if you point multiple
@@ -154,26 +154,26 @@ Possible types are:
 
 .. raw:: html
 
-   <h2>Site</h2>
+  <h2>Site</h2>
 
 Every Webhook has a ``site`` parameter that identifies which Talkable site sent
 this request. This is useful if you have a multi-site setup or use a staging site.
 
 .. raw:: html
 
-   <h2 id="talkable_ips">Whitelisting Talkable IPs</h2>
+  <h2 id="talkable_ips">Whitelisting Talkable IPs</h2>
 
 In case your servers are behind firewall, you may need to whitelist Talkable IP
 addresses so webhooks can be delivered. Pass list of these addresses to your network administrator:
 
 .. hlist::
-   :columns: 4
+  :columns: 4
 
-   .. include:: /partials/talkable_ip_list.rst
+  .. include:: /partials/talkable_ip_list.rst
 
 .. raw:: html
 
-   <h2>Compatibility and Versioning</h2>
+  <h2>Compatibility and Versioning</h2>
 
 Talkable Webhooks do not currently incorporate versioning. Current spec will not
 be changed for all existing hooks. Note that Talkable may add additional data
@@ -187,14 +187,14 @@ See available Webhooks on the navigation sidebar.
 
 .. container:: hidden
 
-   .. toctree::
-
-      Create Coupons <web_hooks/create_coupon>
-      Referral <web_hooks/referral>
-      Reward <web_hooks/reward>
-      Post Share <web_hooks/post_share>
-      Advocate Signup <web_hooks/offer_signup>
-      Friend Email Gating <web_hooks/claim_signup>
-      Unsubscribe <web_hooks/unsubscribe>
-      Check Unsubscribe <web_hooks/check_unsubscribe>
-      Event <web_hooks/event>
+  .. toctree::
+
+    Create Coupons <web_hooks/create_coupon>
+    Referral <web_hooks/referral>
+    Reward <web_hooks/reward>
+    Post Share <web_hooks/post_share>
+    Advocate Signup <web_hooks/offer_signup>
+    Friend Email Gating <web_hooks/claim_signup>
+    Unsubscribe <web_hooks/unsubscribe>
+    Check Unsubscribe <web_hooks/check_unsubscribe>
+    Event <web_hooks/event>
diff --git a/source/web_hooks/check_unsubscribe.rst b/source/web_hooks/check_unsubscribe.rst
index fdd982b59..d2fbac568 100644
--- a/source/web_hooks/check_unsubscribe.rst
+++ b/source/web_hooks/check_unsubscribe.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Check Unsubscribe Webhook ensures that emails are not sent to unsubscribed users.
+  :description: Check Unsubscribe Webhook ensures that emails are not sent to unsubscribed users.
 
 Check Unsubscribe Webhook
 =========================
@@ -14,7 +14,7 @@ from Talkable referral related emails at any time from those emails directly.
 
 .. raw:: html
 
-   <h2>When does Talkable call the Check Unsubscribe Webhook?</h2>
+  <h2>When does Talkable call the Check Unsubscribe Webhook?</h2>
 
 Talkable Check Unsubscribe Webhook is triggered on every attempt to send an
 otherwise valid customer email, aimed at checking if the email is also valid on
@@ -22,25 +22,25 @@ merchant side.
 
 .. important::
 
-   If this Check Unsubscribe Webhook is used, the response JSON returned by
-   merchant must contain the following fields:
+  If this Check Unsubscribe Webhook is used, the response JSON returned by
+  merchant must contain the following fields:
 
    .. code-block:: javascript
 
-      { "result": { "unsubscribed": true } }
+     { "result": { "unsubscribed": true } }
 
    The 'unsubscribed' field should have a boolean value,
    representing unsubscribed status according to the merchant info.
 
 .. raw:: html
 
-   <h2>Payload parameters provided</h2>
+  <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Check Unsubscribe Webhook is available here: `Check Unsubscribe Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Check%20Unsubscribe/post_your_api_check_unsubscribe_web_hook_path>`_.
 
 .. raw:: html
 
-   <h3>View categories</h3>
+  <h3>View categories</h3>
 
 View category can be one of the following:
 
@@ -53,4 +53,4 @@ View category can be one of the following:
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/claim_signup.rst b/source/web_hooks/claim_signup.rst
index a2c36b2b6..ec7efe3b6 100644
--- a/source/web_hooks/claim_signup.rst
+++ b/source/web_hooks/claim_signup.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Friend Email Gating Webhook notifies your endpoint that Friend email gating form was submitted.
+  :description: Friend Email Gating Webhook notifies your endpoint that Friend email gating form was submitted.
 
 Friend Email Gating Webhook
 ===========================
@@ -20,7 +20,7 @@ Use cases for the Friend Email Gating Webhook include:
 
 .. raw:: html
 
-   <h2>When does Talkable call the Friend Email Gating Webhook?</h2>
+  <h2>When does Talkable call the Friend Email Gating Webhook?</h2>
 
 Talkable Friend Email Gating Webhook is triggered any time an Friend Email
 Gating form is submitted. This is the form a Friend completes after receiving
@@ -29,15 +29,15 @@ a share from an Advocate, and before receiving their discount code.
 Friend Email Gating form example:
 
 .. image:: /_static/img/friend_email_gating_form.png
-   :alt: Friend Email Gating Form
-   :class: is-minimal
+  :alt: Friend Email Gating Form
+  :class: is-minimal
 
 .. raw:: html
 
-   <h2>Payload parameters provided</h2>
+  <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Friend Email Gating Webhook is available here: `Friend Email Gating Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Friend%20Email%20Gating/post_your_api_claim_signup_web_hook_path>`_.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/create_coupon.rst b/source/web_hooks/create_coupon.rst
index f2114591f..f420060d8 100644
--- a/source/web_hooks/create_coupon.rst
+++ b/source/web_hooks/create_coupon.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Create Coupon Webhook enables automatic coupon creation. That means you are no longer need to upload coupon lists into the Talkable platform manually.
+  :description: Create Coupon Webhook enables automatic coupon creation. That means you are no longer need to upload coupon lists into the Talkable platform manually.
 
 Create Coupon Webhook
 =====================
@@ -19,7 +19,7 @@ on their platform.
 
 .. raw:: html
 
-   <h2>When does Talkable call the Create Coupon Webhook?</h2>
+  <h2>When does Talkable call the Create Coupon Webhook?</h2>
 
 Create Coupon Webhook is called when the quantity of available coupons drops
 below a Talkable threshold.
@@ -39,7 +39,7 @@ a successful response.
 
 .. raw:: html
 
-   <h2>Set Up</h2>
+  <h2>Set Up</h2>
 
 The Create Coupon Webhook will add coupons to a specific coupon list on Talkable’s
 backend. These coupon lists must be set up in the Talkable campaign editor before
@@ -52,8 +52,8 @@ coupon list for a campaign:
    incentives for both Advocate and Friend can be configured
 
 .. image:: /_static/img/advocate_referral_incentive.png
-   :alt: Edit Referral Incentives
-   :class: is-minimal
+  :alt: Edit Referral Incentives
+  :class: is-minimal
 
 3. Inside the Referral Incentive Editor choose the **Coupon code type: Single-use**
    then select an existing Coupon list or create a new coupon list by clicking
@@ -67,10 +67,10 @@ coupon list for a campaign:
 
 .. note::
 
-   Coupons created by the **Create Coupon Webhook** will be added to the coupon
-   list associated with the referral campaign. Multiple referral campaigns can
-   use the same or unique coupon lists. **Advocate** and **Friend** referral
-   incentives can also use the same or unique coupon lists.
+  Coupons created by the **Create Coupon Webhook** will be added to the coupon
+  list associated with the referral campaign. Multiple referral campaigns can
+  use the same or unique coupon lists. **Advocate** and **Friend** referral
+  incentives can also use the same or unique coupon lists.
 
 Once a single-use coupon code list is associated with a campaign, then the
 Create Coupon Webhook can now be set up.
@@ -78,10 +78,10 @@ Create Coupon Webhook can now be set up.
 
 .. raw:: html
 
-   <h2>Payload parameters provided by Create Coupon Webhook</h2>
+  <h2>Payload parameters provided by Create Coupon Webhook</h2>
 
 The sample payload with parameters for Create Coupon Webhook is available here: `Create Coupon Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Create%20Coupon/post_your_api_create_coupon_web_hook_path>`_.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/event.rst b/source/web_hooks/event.rst
index 16815c0e5..80f76c4ec 100644
--- a/source/web_hooks/event.rst
+++ b/source/web_hooks/event.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Event Webhook lets you know when a purchase was made.
+  :description: Event Webhook lets you know when a purchase was made.
 
 Event Webhook
 =============
@@ -19,7 +19,7 @@ Use cases for the Event Webhook include:
 
 .. raw:: html
 
-   <h2>When does Talkable call the Event Webhook?</h2>
+  <h2>When does Talkable call the Event Webhook?</h2>
 
 Talkable calls the Event Webhook any time an Event or a Purchase
 is registered either via :ref:`the front-end Talkable integration <advanced_features/events>`
@@ -27,11 +27,11 @@ or using the :ref:`Talkable backend API <api_v2/origins>`.
 
 .. raw:: html
 
-   <h2>Payload parameters provided</h2>
+  <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Event Webhook is available here: `Event Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Event/post_your_api_event_web_hook_path>`_.
 
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/offer_signup.rst b/source/web_hooks/offer_signup.rst
index 5f735b616..c2b2b1fc6 100644
--- a/source/web_hooks/offer_signup.rst
+++ b/source/web_hooks/offer_signup.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Advocate Signup Webhook notifies your endpoint of an Advocate signup forms submission.
+  :description: Advocate Signup Webhook notifies your endpoint of an Advocate signup forms submission.
 
 Advocate Signup Webhook
 =======================
@@ -19,7 +19,7 @@ Use cases for the Advocate Signup Webhook include:
 
 .. raw:: html
 
-   <h2>When does Talkable call the Advocate Signup Webhook?</h2>
+  <h2>When does Talkable call the Advocate Signup Webhook?</h2>
 
 Talkable Signup Webhook is triggered any time an Advocate Signup Form is
 submitted. The Advocate Signup Form is the standard Name & Email (with optional
@@ -29,15 +29,15 @@ and sharing an offer with Friends.
 Advocate Signup Form example:
 
 .. image:: /_static/img/advocate_signup_form_webhook.png
-   :alt: Advocate Signup Form,
-   :class: is-minimal
+  :alt: Advocate Signup Form,
+  :class: is-minimal
 
 .. raw:: html
 
-   <h2>Payload parameters provided for Advocate Signup Webhook</h2>
+  <h2>Payload parameters provided for Advocate Signup Webhook</h2>
 
 The sample payload with parameters for Advocate Signup Webhook is available here: `Advocate Signup Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Advocate%20Signup/post_your_api_advocate_signup_web_hook_path>`_.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/post_share.rst b/source/web_hooks/post_share.rst
index a83fb68a7..c34892eeb 100644
--- a/source/web_hooks/post_share.rst
+++ b/source/web_hooks/post_share.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Post Share Webhook provides notification of share events performed within a referral campaign workflow.
+  :description: Post Share Webhook provides notification of share events performed within a referral campaign workflow.
 
 Post Share Webhook
 ==================
@@ -16,7 +16,7 @@ within a referral campaign workflow. Use cases for the Post Share Webhook includ
 
 .. raw:: html
 
-   <h2>When does Talkable call the Post Share Webhook?</h2>
+  <h2>When does Talkable call the Post Share Webhook?</h2>
 
 Talkable Post Share Webhook is triggered any time an |advocate| (referrer)
 shares offer details with a |friend| (referee) via the corresponding form
@@ -33,17 +33,17 @@ triggered twice.
 
 .. raw:: html
 
-   <h2>Payload parameters provided for Post Share Webhook</h2>
+  <h2>Payload parameters provided for Post Share Webhook</h2>
 
 The sample payload with parameters for Post Share Webhook is available here: `Post Share Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Post%20Share/post_your_api_post_share_web_hook_path>`_.
 
 .. note::
 
-   ``origin.email`` contains the email saved at the moment when the campaign is
-   first shown to the Advocate. It could be ``null``. For the most up-to-date
-   information about the Advocate, use ``sharer_info`` property which is updated
-   with the email address the Advocate has entered on the Advocate Signup/Share Page.
+  ``origin.email`` contains the email saved at the moment when the campaign is
+  first shown to the Advocate. It could be ``null``. For the most up-to-date
+  information about the Advocate, use ``sharer_info`` property which is updated
+  with the email address the Advocate has entered on the Advocate Signup/Share Page.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/referral.rst b/source/web_hooks/referral.rst
index bb2b4e04f..69bb383de 100644
--- a/source/web_hooks/referral.rst
+++ b/source/web_hooks/referral.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Referral Webhook notifies your endpoint that your brand Advocate’s referral status has become “Approved”.
+  :description: Referral Webhook notifies your endpoint that your brand Advocate’s referral status has become “Approved”.
 
 Referral Webhook
 ================
@@ -25,7 +25,7 @@ Use cases for the Referral Webhook include:
 
 .. note::
 
-   “Approved” referral status does not guarantee that Advocate will receive a reward.
+  “Approved” referral status does not guarantee that Advocate will receive a reward.
 
 Things that can prevent Advocate or Friend from being rewarded:
 
@@ -37,25 +37,25 @@ Things that can prevent Advocate or Friend from being rewarded:
 
 .. important::
 
-   Referral Webhook keeps retrying until it gets 2xx HTTP status in response.
-   Only after that rewards associated with the referral can be paid.
+  Referral Webhook keeps retrying until it gets 2xx HTTP status in response.
+  Only after that rewards associated with the referral can be paid.
 
 .. raw:: html
 
-   <h2>When does Talkable call the Referral Webhook?</h2>
+  <h2>When does Talkable call the Referral Webhook?</h2>
 
 Talkable Referral Webhook is triggered any time an Advocate referral status has become
 “Approved” specifically for a Friend purchase or event.
 
 .. note::
 
-   Referral Webhook triggers only for Advocate rewards specifically from a Friend
-   Purchase or Friend Event (such as signup event or subscription purchase event).
-   To receive notification of both Advocate and Friend rewards use the Rewards Webhook.
+  Referral Webhook triggers only for Advocate rewards specifically from a Friend
+  Purchase or Friend Event (such as signup event or subscription purchase event).
+  To receive notification of both Advocate and Friend rewards use the Rewards Webhook.
 
 .. raw:: html
 
-   <h2>Payload parameters provided for Referral Webhook</h2>
+  <h2>Payload parameters provided for Referral Webhook</h2>
 
 The sample payload with parameters for Referral Webhook is available here: `Referral Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Referral/post_your_api_referral_web_hook_path>`_.
 
@@ -65,4 +65,4 @@ The sample payload with parameters for Referral Webhook is available here: `Refe
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/reward.rst b/source/web_hooks/reward.rst
index 24dd1d351..5c11dc5a2 100644
--- a/source/web_hooks/reward.rst
+++ b/source/web_hooks/reward.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Reward Webhook notifies your endpoint that a reward is ready to be given, or it has been already given.
+  :description: Reward Webhook notifies your endpoint that a reward is ready to be given, or it has been already given.
 
 Reward Webhook
 ==============
@@ -21,7 +21,7 @@ Use cases for the Reward Webhook include:
 
 .. raw:: html
 
-   <h2>When does Talkable call the Reward Webhook?</h2>
+  <h2>When does Talkable call the Reward Webhook?</h2>
 
 Talkable calls the Reward Webhook any time a reward is ready to be, or has been
 given to either an Advocate or a Friend according to the logic set-up in a
@@ -35,20 +35,20 @@ Possible events which will trigger the Reward Webhook are:
 
   .. note::
 
-     If campaign is setup without email gating form, Reward Webhook with
-     Reason = click will trigger when Friend clicks through to site.
+    If campaign is setup without email gating form, Reward Webhook with
+    Reason = click will trigger when Friend clicks through to site.
 
 * Friend makes eligible purchase (Reason = **referrer**)
 * Friend makes eligible purchase (Reason = **referred**)
 
   .. note::
 
-     Reason = referrer indicates a reward should be given to an Advocate.
-     Reason = referred indicates a reward should be given to a Friend.
+    Reason = referrer indicates a reward should be given to an Advocate.
+    Reason = referred indicates a reward should be given to a Friend.
 
 .. raw:: html
 
-   <h2>Set-Up</h2>
+  <h2>Set-Up</h2>
 
 Because the Reward Webhook will trigger at various events depending on the
 Incentive configuration for each referral campaign, to trigger the Reward
@@ -61,8 +61,8 @@ To configure incentives:
    incentives for both Advocates and Friends can be set-up
 
 .. image:: /_static/img/advocate_referral_incentive.png
-   :alt: Edit Referral Incentives,
-   :class: is-minimal
+  :alt: Edit Referral Incentives,
+  :class: is-minimal
 
 3. Configure the incentives as desired inside the Referral Incentive Editor.
    To configure Incentive types other than Coupon Codes, please contact your
@@ -71,12 +71,12 @@ To configure incentives:
 
 .. note::
 
-   If there is a delay configured into when the Advocate reward is approved then
-   the Reward Webhook trigger when the Advocate reward is ready to be, or has
-   been given. For example, if campaigns are set to send an Advocate their reward
-   three days after a Friend makes an eligible purchase, then the Reward Webhook
-   will be called three days after the Friend makes the eligible purchase. You
-   can select these delays under **Fraud Settings**, which is found under **Menu**.
+  If there is a delay configured into when the Advocate reward is approved then
+  the Reward Webhook trigger when the Advocate reward is ready to be, or has
+  been given. For example, if campaigns are set to send an Advocate their reward
+  three days after a Friend makes an eligible purchase, then the Reward Webhook
+  will be called three days after the Friend makes the eligible purchase. You
+  can select these delays under **Fraud Settings**, which is found under **Menu**.
 
 Once incentives are configured for a referral campaign, Talkable will then call
 the Reward Webhook any time either an Advocate or a Friend should receive a
@@ -85,13 +85,13 @@ Webhook Set Up Steps <web_hooks>`
 
 .. raw:: html
 
-   <h2>Payload parameters provided by Reward Webhook</h2>
+  <h2>Payload parameters provided by Reward Webhook</h2>
 
 The sample payload with parameters for Reward Webhook is available here: `Reward Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Reward/post_your_api_reward_web_hook_path>`_.
 
 .. raw:: html
 
-   <h2>Reasons</h2>
+  <h2>Reasons</h2>
 
 Reward reason can be of 5 following general types.
 
@@ -107,4 +107,4 @@ Reward reason can be of 5 following general types.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::
diff --git a/source/web_hooks/unsubscribe.rst b/source/web_hooks/unsubscribe.rst
index f4b66c7c5..70e3b4a36 100644
--- a/source/web_hooks/unsubscribe.rst
+++ b/source/web_hooks/unsubscribe.rst
@@ -2,7 +2,7 @@
 .. include:: /partials/common.rst
 
 .. meta::
-   :description: Unsubscribe Webhook notifies you that a user has unsubscribed from Talkable referral email.
+  :description: Unsubscribe Webhook notifies you that a user has unsubscribed from Talkable referral email.
 
 Unsubscribe Webhook
 ===================
@@ -19,17 +19,17 @@ Use cases for the Unsubscribe Webhook include:
 
 .. raw:: html
 
-   <h2>When does Talkable call the Unsubscribe Webhook?</h2>
+  <h2>When does Talkable call the Unsubscribe Webhook?</h2>
 
 Talkable Unsubscribe Webhook is called any time a user unsubscribes from a
 Talkable sent email.
 
 .. raw:: html
 
-   <h2>Payload parameters provided</h2>
+  <h2>Payload parameters provided</h2>
 
 The sample payload with parameters for Unsubscribe Webhook is available here: `Unsubscribe Webhook Payload <https://www.talkable.com/api-docs/index.html?urls.primaryname=webhooks%20api&urls.primaryName=Webhooks#/Unsubscribe/post_your_api_unsubscribe_web_hook_path>`_.
 
 .. container:: hidden
 
-   .. toctree::
+  .. toctree::