Merge pull request #671 from segmentio/repo-sync

repo sync

Author: bot-docsteam

.yarn/cache/minimist-npm-1.2.5-ced0e1f617-86706ce5b3.zip

@@ -2,11 +2,11 @@
 {% assign currentIntegration = site.data.catalog.sources.items | where: "slug", currentSlug | first %}
 {% if currentIntegration.url contains "cloud-apps" or page.path contains "cloud-apps" %}
 {% if currentIntegration.isCloudEventSource  %}
-<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Good to know: Event source</p>
+<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Good to know: Event Cloud source</p>
 <p markdown=1>The {{ page.title }} is an **event** source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and **also** sent to  Segment streaming destinations. [Learn more about cloud sources.](/docs/connections/sources/#cloud-apps)</p>
 </div></div>
 {% else %}
 
-<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Good to know: Object source</p><p markdown=1>The {{ page.title }} is an **object** source. This means that it sends information (traits) about a thing that exists and persists over time, such as a person or company, and which can be updated over time. Data from this source can only be exported directly to a warehouse, but it can then be used for further analysis. [Learn more about cloud sources.](/docs/connections/sources/#cloud-apps)</p></div></div>
+<div class="premonition success"><div class="fa fa-check-square"></div><div class="content"><p class="header">Good to know: Object Cloud source</p><p markdown=1>The {{ page.title }} is an **object** source. This means that it sends information (traits) about a thing that exists and persists over time, such as a person or company, and which can be updated over time. Data from this source can only be exported directly to a warehouse, but it can then be used for further analysis. [Learn more about cloud sources.](/docs/connections/sources/#cloud-apps)</p></div></div>
 {% endif %}
 {% endif %}

src/_includes/content/cloud-app-note.md

@@ -47,7 +47,6 @@ analytics.identify('user_123', {
 {% endcodeexampletab %}
 {% endcodeexample %}
 {% endcomment %}
----
 
 
 ## Types of sources
@@ -57,8 +56,11 @@ Segment has five types of sources:
 * [Mobile](#mobile)
 * [Server](#server)
 * [Cloud App](#cloud-apps)
+  * [Object Cloud](#object-cloud-sources)
+  * [Event Cloud](#event-cloud-sources)
 * User-created [Source Functions](/docs/connections/sources/source-functions/)
 
+
 Web, Mobile, and Server sources send first-party data from your digital properties. Cloud-app sources send data about your users from your connected web apps such as [Zendesk](/docs/connections/sources/catalog/cloud-apps/zendesk/),  [Stripe](/docs/connections/sources/catalog/cloud-apps/stripe/), and [Braze](/docs/connections/sources/catalog/cloud-apps/braze/).
 
 ## Create a source
@@ -80,7 +82,7 @@ To create a source:
   description="Analytics and data collection is a very broad topic and it can be quite overwhelming. How do you get started?"
 %}
 
----
+
 
 ## Mobile
 
@@ -95,7 +97,7 @@ Segment's Mobile SDKs are the best way to simplify your iOS, Android, and Xamari
 - [Swift](/docs/connections/sources/catalog/libraries/mobile/swift-ios/)
 - [Xamarin](/docs/connections/sources/catalog/libraries/mobile/xamarin)
 
----
+
 
 ## Server
 
@@ -114,7 +116,7 @@ Segment's server-side sources let you send analytics data directly from your ser
 > info "Cloud-mode tracking"
 > Server-side data management is when tag sends data to the Segment servers, which then passes that data to the destination system.
 
----
+
 
 ## Cloud Apps
 
@@ -151,11 +153,11 @@ If Segment doesn't have a library for your environment, you can send your data d
 
 Segment's [Pixel Tracking API](/docs/connections/sources/catalog/libraries/server/pixel-tracking-api/) lets you track events from environments where you can't execute code, like tracking email opens.
 
-| Event name              | Description       |
-| ---                     | ---               |
-| Email Delivered         | The message has been successfully delivered to the receiving server |
-| Email Opened	          | The recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event. |
-| Email Link Clicked      | The recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event. |
-| Email Bounced           | The receiving server could not or would not accept message. |
-| Email Marked as Spam    | The recipient marked message as spam. |
-| Unsubscribe             | The recipient clicked on message's subscription management link. |
+| Event name           | Description                                                                                                           |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| Email Delivered      | The message has been successfully delivered to the receiving server.                                                   |
+| Email Opened         | The recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event.           |
+| Email Link Clicked   | The recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event. |
+| Email Bounced        | The receiving server could not or would not accept message.                                                           |
+| Email Marked as Spam | The recipient marked message as spam.                                                                                 |
+| Unsubscribe          | The recipient clicked on message's subscription management link.                                                      |