Replaced marketing section with Engage section

Author: eshanrnh

13/umbraco-engage/developers/personalization/segment-information.md

@@ -35,6 +35,7 @@ The `PageView` lies at the heart of Umbraco Engage Analytics feature and exposes
 Consider the following example (continued from above) where the content of content type "`Home`" was requested. We will now tell Umbraco to execute this custom code whenever the template `HomeTemplate` is requested:
 
 {% code overflow="wrap" %}
+
 ```csharp
 public ActionResult HomeTemplate()
 {
@@ -49,23 +50,26 @@ public ActionResult HomeTemplate()
     ...
 }
 ```
+
 {% endcode %}
 
 We can for example check if the current visitor falls into a segment called "**MySegment**". Keep in mind that a visitor can fall into any number of segments (zero, one, or all). A segment alone don't anything and can be regarded as purely informational, or as a "**Flag**" or "**Label**".
 
 The personalization used by the Umbraco Engage to modify the appearance of a page is called **Applied Personalization**.
 
-A page request can have only **one** active Applied Personalization. Based on the current segments (and their sort order), Umbraco Engage picks the first applicable Applied Personalization. This could be a multi-doctype or multi-page personalization (Marketing section) or single-page personalization (content).
+A page request can have only **one** active Applied Personalization. Based on the current segments (and their sort order), Umbraco Engage picks the first applicable Applied Personalization. This could be a multi-doctype or multi-page personalization (Engage section) or single-page personalization (content).
 
 To inspect the resolved Applied Personalization, we can use the property `AppliedPersonalization` on the state's **PageView**:
 
 {% code overflow="wrap" %}
+
 ```csharp
 if (analyticsState.Pageview.AppliedPersonalization != null && analyticsState.Pageview.AppliedPersonalization.Name == "MyAppliedPersonalization")
 {
     ...
 }
 ```
+
 {% endcode %}
 
 Be aware that no personalization may have been resolved for the current request. Make sure to do a **null check** before reading the `AppliedPersonalization` property. The property `SegmentId` will tell you which active segment was responsible for triggering the Applied Personalization.

13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md

@@ -8,7 +8,7 @@ description: >-
 
 # Monitor the A/B Test
 
-When the A/B test is running it is advised to check the progress regularly. This can be done on the specific page or via the Marketing Section.
+When the A/B test is running it is advised to check the progress regularly. This can be done on the specific page or via the Engage Section.
 
 If you go to the overview you can see all running tests. The overview includes the following information:
 

13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md

@@ -13,7 +13,7 @@ Setting up an A/B test in Umbraco Engage requires no code or need for any extern
 Starting A/B tests can be done in two ways:
 
 * Initiate a Single Page, Multiple Page, or Document Type test via the Content App on the specific page,
-* Initiate Multipage and Document Type tests via the Marketing section.
+* Initiate Multipage and Document Type tests via the Engage section.
 
 ## Set up the test
 

13/umbraco-engage/marketers-and-editors/settings/README.md

@@ -23,4 +23,4 @@ Get an overview of all configured settings of Umbraco Engage.
 
 ## [Permissions](permissions.md)
 
-Explore how to control which Umbraco user groups have access to the Marketing section settings and manage where content apps are displayed.
+Explore how to control which Umbraco user groups have access to the Engage section settings and manage where content apps are displayed.