more of these

Author: forstisabella

src/connections/storage/catalog/data-lakes/index.md

@@ -11,7 +11,7 @@ Segment supports two type of data-lakes:
 - [AWS Data Lakes](/docs/connections/storage/catalog/data-lakes/#set-up-segment-data-lakes)
 - [Segment Data Lakes (Azure)](/docs/connections/storage/catalog/data-lakes/#set-up-segment-data-lakes-azure)
 
-> note "Lake Formation"
+> success ""
 > You can also set up your Segment Data Lakes using [Lake Formation](/docs/connections/storage/data-lakes/lake-formation/), a fully managed service built on top of the AWS Glue Data Catalog.
 
 ## Set up Segment Data Lakes (AWS)
@@ -167,7 +167,7 @@ Before you can configure your Azure resources, you must complete the following p
 
 ### Step 4 - Set up Databricks
 
-> note "Databricks pricing tier"
+> info "Databricks pricing tier"
 > If you create a Databricks instance only for Segment Data Lakes (Azure) usage, only the standard pricing tier is required. However, if you use your Databricks instance for other applications, you may require premium pricing.
 
 1. From the [home page of your Azure portal](https://portal.azure.com/#home){:target="_blank”}, select **Create a resource**.
@@ -346,7 +346,7 @@ After you set up the necessary resources in Azure, the next step is to set up th
 
 Instead of manually configuring your Data Lake, you can create it using the script in the [`terraform-segment-data-lakes`](https://github.com/segmentio/terraform-segment-data-lakes){:target="_blank”} GitHub repository.
 
-> note " "
+> warning ""
 > This script requires Terraform versions 0.12+.
 
 Before you can run the Terraform script, create a Databricks workspace in the Azure UI using the instructions in [Step 4 - Set up Databricks](#step-4---set-up-databricks). Note the **Workspace URL**, as you will need it to run the script.

src/connections/storage/data-lakes/data-lakes-manual-setup.md

@@ -79,7 +79,7 @@ Segment requires access to an EMR cluster to perform necessary data processing.
 14. Expand the EC2 security groups section and select the appropriate security groups for the Master and Core & Task types.
 15. Select **Create cluster**.
 
-> note ""
+> info ""
 > If you update the EMR cluster of existing Data Lakes instance, take note of the EMR cluster ID on the confirmation page.
 
 ## Step 3 - Create an Access Management role and policy
@@ -119,7 +119,7 @@ Attach the following trust relationship document to the role to create a `segmen
 }
 ```
 
-> note ""
+> info ""
 > Replace the `ExternalID` list with the Segment `WorkspaceID` that contains the sources to sync to the Data Lake.
 
 ### IAM policy
@@ -210,7 +210,7 @@ Add a policy to the role created above to give Segment access to the relevant Gl
 }
 ```
 
-> note ""
+> warning ""
 > The policy above grants full access to Athena, but the individual Glue and S3 policies determine which table is queried. Segment queries for debugging purposes, and notifies you before running any queries.
 
 ## Debugging

src/connections/storage/data-lakes/lake-formation.md

@@ -46,7 +46,7 @@ To verify that you've configured Lake Formation, open the [AWS Lake Formation se
 
 ### Configure Lake Formation using IAM policies
 
-> note "Granting Super permission to IAM roles"
+> info "Granting Super permission to IAM roles"
 > If you manually configured your database, assign the `EMR_EC2_DefaultRole` Super permissions in step 8. If you configured your database using Terraform, assign the `segment_emr_instance_profile` Super permissions in step 8.
 
 #### Existing databases

src/connections/storage/warehouses/health.md

@@ -11,8 +11,8 @@ You can use this feature to answer questions such as:
 - *Anomaly detection* - How much data is being synced on a daily basis? Have there been anomalous spikes or dips that may indicate sudden changes in event volume, sync failures, or something else?
 - *Data composition* - Which sources are contributing the most (or least) amount of data in my warehouse? Which collections make up the majority of data within a source?
 
-> note ""
-> **Note**: Warehouse Health is available for all Warehouse customers.
+> success ""
+> Warehouse Health is available for all Warehouse customers.
 
 
 The Warehouse Health dashboards are available at both the [warehouse level](#warehouse-dashboards), and at the [warehouse-source connection level](#warehouse-source-dashboards), explained below.

src/connections/storage/warehouses/redshift-useful-sql.md

@@ -19,7 +19,7 @@ You can use SQL queries for the following tasks:
   - [Historical Traits](#historical-traits-1)
   - [Converting the Groups Table into an Organizations Table](#converting-the-groups-table-into-an-organizations-table)
 
-> note " "
+> success " "
 > If you're looking for SQL queries for warehouses other than Redshift, check out some of Segment's [Analyzing with SQL guides](/docs/connections/storage/warehouses#analyzing-with-sql).
 
 ## Tracking events

src/connections/storage/warehouses/schema.md

@@ -5,8 +5,9 @@ title: Warehouse Schemas
 A **schema** describes the way that the data in a warehouse is organized. Segment stores data in relational schemas, which organize data into the following template:
 `<source>.<collection>.<property>`, for example `segment_engineering.tracks.user_id`, where source refers to the source or project name (segment_engineering), collection refers to the event (tracks), and the property refers to the data being collected (user_id). All schemas convert collection and property names from `CamelCase` to `snake_case` using the [go-snakecase](https://github.com/segmentio/go-snakecase) package.
 
-> note "Warehouse column creation"
-> **Note:** Segment creates tables for each of your custom events in your warehouse, with columns for each event's custom properties. Segment does not allow unbounded `event` or `property` spaces in your data. Instead of recording events like "Ordered Product 15", use a single property of "Product Number" or similar.
+> info "Warehouse column creation"
+> Segment creates tables for each of your custom events in your warehouse, with columns for each event's custom properties. Segment does not allow unbounded `event` or `property` spaces in your data. Instead of recording events like "Ordered Product 15", use a single property of "Product Number" or similar.
+> 
 > Segment creates and populates a column only when it receives a non-null value from the source.
 
 ### How warehouse tables handle nested objects and arrays

src/connections/storage/warehouses/warehouse-syncs.md

@@ -23,8 +23,8 @@ Your plan determines how frequently data is synced to your warehouse.
 
 *If you're a Business plan member and would like to adjust your sync frequency, you can do so using the Selective Sync feature. To enable Selective Sync, please go to **Warehouse** > **Settings** > **Sync Schedule**. 
 
-> note "Why can't I sync more than 24 times per day?"
-> We do not set syncs to happen more than once per hour (24 times per day). The warehouse product is not designed for real-time data, so more frequent syncs would not necessarily be helpful.
+> info "Why can't I sync more than 24 times per day?"
+> Segment does not set syncs to happen more than once per hour (24 times per day). The warehouse product is not designed for real-time data, so more frequent syncs would not necessarily be helpful.
 
 ## Sync History
 You can use the Sync History page to see the status and history of data updates in your warehouse. The Sync History page is available for every source connected to each warehouse. This page helps you answer questions like, “Has the data from a specific source been updated recently?” “Did a sync completely fail, or only partially fail?” and “Why wasn't this sync successful?”
@@ -61,8 +61,8 @@ Warehouse Selective Sync allows you to manage the data that you send to your war
 
 With Selective Sync, you can customize which collections and properties from a source are sent to each warehouse. This helps you control the data that is sent to each warehouse, allowing you to sync different sets of data from the same source to different warehouses.
 
-> note ""
-> **NOTE:** This feature only affects [warehouses](/docs/connections/storage/warehouses/), and doesn't prevent data from going to any other [destinations](/docs/connections/destinations/).
+> info ""
+> This feature only affects [warehouses](/docs/connections/storage/warehouses/), and doesn't prevent data from going to any other [destinations](/docs/connections/destinations/).
 
 When you disable a source, collection or property, Segment no longer syncs data from that source. Segment won't delete any historical data from your warehouse. When you re-enable a source, Segment syncs all events since the last sync. This doesn't apply when a collection or property is re-enabled. Only new data generated after re-enabling a collection or property will sync to your warehouse.
 

src/engage/content/email/template.md

@@ -29,7 +29,7 @@ To configure an email template, click **Create Template**.
 
 1. Select **Email**, and click **Configure**.
 
-> note ""
+> info ""
 > You must first connect a [SendGrid subuser account](https://docs.sendgrid.com/ui/account-and-settings/subusers#create-a-subuser){:target="blank"} to your Segment space to build email templates in Engage. Visit the [onboarding steps](/docs/engage/onboarding/) for more information.
 
 2. Configure the email template.

src/engage/journeys/step-types.md

@@ -111,7 +111,7 @@ The **Send an email**, **Send an SMS**, and **Send a WhatsApp** steps are only a
 
 Use Twilio Engage to send email as a step in a Journey.
 
-> note ""
+> info ""
 > To send email in Engage, you must connect a [SendGrid subuser account](https://docs.sendgrid.com/ui/account-and-settings/subusers#create-a-subuser){:target="blank"} to your Segment space. Visit the [onboarding steps](/docs/engage/onboarding/) for more information.
 
 1. From the **Add step** window, **Send an email**.
@@ -132,7 +132,7 @@ Use Twilio Engage to send email as a step in a Journey.
 
 Use Twilio Engage to send an SMS message as a step in a Journey.
 
-> note ""
+> info ""
 > To send SMS in Engage, you must connect a Twilio messaging service to your Segment workspace. Visit the [onboarding steps](/docs/engage/onboarding/) for more information.
 
 1. From the **Add step** window, click **Send an SMS**.

src/getting-started/02-simple-install.md

@@ -70,12 +70,10 @@ Click a tab below to see the tutorial content for the specific library you chose
 
 ### Step 1: Copy the Snippet
 <br>
-Navigate **Connections > Sources > JavaScript** in the Segment app and copy the snippet from the JavaScript Source overview page and paste it into the `<head>` tag of your site.
+Navigate to **Connections > Sources > JavaScript** in the Segment app, copy the snippet from the JavaScript Source overview page, and paste it into the `<head>` tag of your site.
 <br><br>
 That snippet loads Analytics.js onto the page _asynchronously_, so it won't affect your page load speed. Once the snippet runs on your site, you can turn on destinations from the destinations page in your workspace and data starts loading on your site automatically.
 <br><br>
-> note ""
-> **Note:** If you only want the most basic Google Analytics setup you can stop reading right now. You're done! Just toggle on Google Analytics from the Segment App.
 
 > info ""
 > The Segment snippet version history available on [GitHub](https://github.com/segmentio/snippet/blob/master/History.md){:target="_blank"}. Segment recommends that you use the latest snippet version whenever possible.
@@ -85,8 +83,8 @@ That snippet loads Analytics.js onto the page _asynchronously_, so it won't affe
 <br>
 The `identify` method is how you tell Segment who the current user is. It includes a unique User ID and any optional traits you know about them. You can read more about it in the [identify method reference](/docs/connections/sources/catalog/libraries/website/javascript#identify).
 <br><br>
-> note ""
-> **Note:** You don't need to call `identify` for anonymous visitors to your site. Segment automatically assigns them an `anonymousId`, so just calling `page` and `track` works just fine without `identify`.
+> info "You don't need to call `identify` for anonymous visitors to your site"
+> Segment automatically assigns them an `anonymousId`, so just calling `page` and `track` works just fine without `identify`.
 <br><br>
 Here's an example of what a basic call to `identify` might look like:
 
@@ -114,8 +112,8 @@ analytics.identify(' {{user.id}} ', {
 <br>
 With that call in your page footer, you successfully identify every user that visits your site.
 <br><br>
-> note ""
-> **Note:** If you only want to use a basic CRM set up, you can stop here. Just enable Salesforce, Intercom, or any other CRM system from your Segment workspace, and Segment starts sending all of your user data to it.
+> info ""
+> You've completed a basic CRM set up. Return to the Segment app to enable Salesforce, Intercom, or your CRM system of choice and Segment starts sending all of your user data to it.
 
 <br>
 ### Step 3: Track Actions
@@ -209,8 +207,8 @@ Here's an example of what a basic call to `identify` might look like:
 <br>
 This call identifies Michael by his unique User ID (`f4ca124298`, which is the one you know him by in your database) and labels him with `name` and `email` traits.
 <br><br>
-> note ""
-> **Note:** When you put that code in your iOS app, you need to replace those hard-coded trait values with the variables that represent the details of the currently logged-in user.
+> info ""
+> When you put the above code in your iOS app, you would replace those hard-coded trait values with variables that represent the details of the user that's currently signed in.
 <br><br>
 ### Step 3: Track Actions
 <br>
@@ -288,8 +286,8 @@ Segment::init("YOUR_WRITE_KEY");
 You only need to call `init` once when your php file is requested. All of your files then have access to the same `Analytics` client.
 
 
-> note ""
-> **Note:** The default PHP consumer is the [libcurl consumer](/docs/connections/sources/catalog/libraries/server/php/#lib-curl-consumer). If this is not working well for you, or if you have a high-volume project, you might try one of Segment's other consumers like the [fork-curl consumer](/docs/connections/sources/catalog/libraries/server/php/#fork-curl-consumer).
+> info ""
+> Segment's default PHP consumer is the [libcurl consumer](/docs/connections/sources/catalog/libraries/server/php/#lib-curl-consumer). If this is not working well for you or if you have a high-volume project, you might try one of Segment's other consumers like the [fork-curl consumer](/docs/connections/sources/catalog/libraries/server/php/#fork-curl-consumer).
 
 <br>
 ### Step 2: Identify Users