Merge pull request #40 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/sources/catalog/cloud-apps/looker/index.md

@@ -12,9 +12,12 @@ From Segment's end, you will need to create a Looker source, and copy your write
 
 ### Defining Looks
 
-Using this Source, Looker will send Look (query) results into Segment as `identify` calls. This is the only API method that Looker sends to Segment. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. **Note: Arrays are not currently supported. Only properties that are strings or numbers are supported.**
+Using this Source, Looker sends Look (query) results into Segment as `identify` calls. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. 
 
-Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one.
+> note ""
+> **NOTE:** Segment doesn't support arrays. Segment supports properties that are strings or numbers.
+
+When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool overrides the existing trait value with the new one.
 
 Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once  in the last 30 days.