Skip to content

Commit 9bdd8ee

Browse files
authored
Merge pull request #1726 from segmentio/DOC-243
DOC-243
2 parents 1c23148 + f29e4e1 commit 9bdd8ee

File tree

8 files changed

+19
-19
lines changed

8 files changed

+19
-19
lines changed

src/_data/sidenav/main.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ sections:
3434
- path: /guides/duplicate-data
3535
title: Handling duplicate data
3636
- path: /guides/ignore-bots
37-
title: Ignoring internet bots
37+
title: Internet bots
3838
- path: /guides/segment-vs-tag-managers
3939
title: Segment vs. tag managers
4040
- path: /guides/what-is-replay
@@ -90,7 +90,7 @@ sections:
9090
- section_title: Connections
9191
section:
9292
- path: /connections
93-
title: Connections overview
93+
title: Overview
9494
- section_title: The Segment Spec
9595
slug: connections/spec
9696
section:
@@ -215,23 +215,23 @@ sections:
215215
- path: /connections/storage/warehouses/redshift-tuning
216216
title: How do I speed up my redshift queries?
217217
- path: /connections/test-connections
218-
title: How do I test my connections?
218+
title: Testing connections
219219
- path: /connections/data-export-options
220-
title: What are my data export options?
220+
title: Data export options
221221
- path: /connections/destination-data-control
222-
title: How do I use Schema Controls?
222+
title: Using Schema Controls
223223
- path: /connections/event-delivery
224-
title: How do I check if data is reaching a destination?
224+
title: Event Delivery
225225
- path: /connections/find-writekey
226-
title: How do I find my write key?
226+
title: Locate your Write Key
227227
- path: /connections/integration_error_codes
228228
title: Integration error codes
229229
- path: /connections/schema-unique-limits
230-
title: Are there limits on my Segment Schema?
230+
title: Segment Schema limits
231231
- path: /connections/rate-limits
232-
title: Rate Limits and SLA
232+
title: Rate limits and SLA
233233
- path: /connections/data-residency
234-
title: Data Residency
234+
title: Data residency
235235
- section_title: Personas
236236
section:
237237
- path: /personas

src/connections/data-export-options.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "What are my data export options?"
2+
title: "Data export options"
33
---
44

55
There are a few ways to export your Segment data. Segment [Business customers](https://segment.com/business) have the most data flexibility, but our self-service customers also have options.

src/connections/data-residency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Data Residency
2+
title: Data residency
33
---
44
{% include content/plan-grid.md name="data-residency" %}
55

src/connections/destination-data-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "How do I use Schema Controls?"
2+
title: "Using Schema Controls"
33
---
44

55
Once you have enabled Destinations for a given Source, all of the [data](/docs/connections/spec/) you track will be routed to your connected tools and warehouses. If you no longer wish to send all data to a particular Destination, you can disable the Destination from the Source overview page. 

src/connections/event-delivery.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: How do I check if data is reaching a destination?
2+
title: Event Delivery
33
---
44

5-
The Event Delivery tool exists to help customers understand if Segment has encountered any issues delivering your source data to destinations
5+
The Event Delivery tool helps you understand if data is reaching your destinations, and also helps you to see if Segment encountered any issues delivering your source data. 
66

7-
Segment sends billions of events to destinations every week. If we encounter any errors when attempting to deliver your data, we report them in the Event Delivery tool.
7+
Segment sends billions of events to destinations every week. If Segment encounters any errors when attempting to deliver your data, Segment reports them in the Event Delivery tool.
88

99
Here is an example of what the Event Delivery tool looks like:
1010

src/connections/find-writekey.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: How do I find my write key?
2+
title: Locate your Write Key
33
---
44

55
The write key is a unique identifier for each Source. It lets Segment know which Source is sending the data, and which destinations should receive that data.

src/connections/schema-unique-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Are there limits on my Segment Schema?
2+
title: Segment Schema limits
33
---
44

55
**How many unique events can be logged in my Segment Schema table?**

src/connections/test-connections.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "How do I test my connections?"
2+
title: "Testing connections"
33
---
44

55

0 commit comments

Comments
 (0)