Merge pull request #632 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/connections/sources/catalog/libraries/server/clojure/index.md

@@ -51,7 +51,7 @@ The default initialization settings are production-ready.
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/go/index.md

@@ -42,7 +42,7 @@ The default initialization settings are production-ready and queue 20 messages b
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -37,7 +37,7 @@ There is a maximum of `32KB` per normal API request.  The `batch` API endpoint a
 ## Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/java/index.md

@@ -61,7 +61,7 @@ The following examples use [Guava's](https://github.com/google/guava) immutable
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 ## Identify
 
 > note ""

src/connections/sources/catalog/libraries/server/kotlin/index.md

@@ -67,7 +67,7 @@ To get started with the Analytics-Kotlin server library:
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 ## Tracking Methods
 
 Once you've installed the mobile or server Analytics-Kotlin library, you can start collecting data through Segment's tracking methods:

src/connections/sources/catalog/libraries/server/net/index.md

@@ -81,7 +81,7 @@ The default initialization settings are production-ready and queue messages on a
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/php/index.md

@@ -46,7 +46,7 @@ The default PHP consumer is the [lib-curl consumer](#lib-curl-consumer). If this
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/python/index.md

@@ -58,7 +58,7 @@ analytics.send = False
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `https://api.segment.io/v1`
-2. Dublin — `https://events.eu1.segmentapis.com/v1`
+2. Dublin — `https://events.eu1.segmentapis.com/`
 
 ## Identify
 

src/connections/sources/catalog/libraries/server/ruby/index.md

@@ -47,7 +47,7 @@ If you're using Rails, you can stick that initialization logic in `config/initia
 ### Regional configuration
 For Business plans with access to [Regional Segment](/docs/guides/regional-segment), you can use the `host` configuration parameter to send data to the desired region:
 1. Oregon (Default) — `api.segment.io/v1`
-2. Dublin — `events.eu1.segmentapis.com/v1/`
+2. Dublin — `events.eu1.segmentapis.com/`
 
 ## Identify
 

src/guides/regional-segment.md

@@ -24,7 +24,7 @@ Regional Data Ingestion enables you to send data to Segment from both Device-mod
 > [Cloud event](/docs/connections/sources/#event-cloud-sources) sources aren't supported in EU workspaces.
 
 ### Client-side sources
-You can configure Segment's client-side SDKs for JavaScript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Data Ingestion Region in that source's settings. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `events.eu1.segmentapis.com/v1` endpoint.
+You can configure Segment's client-side SDKs for JavaScript, iOS, Android, and React Native sources to send data to a regional host after you've updated the Data Ingestion Region in that source's settings. Segment's EU instance only supports data ingestion from Dublin, Ireland with the `events.eu1.segmentapis.com/` endpoint.
 
 > info ""
 > For workspaces that use the EU West Data Processing region, the Dublin Ingestion region is preselected for all sources.
@@ -36,7 +36,7 @@ To set your Data Ingestion Region:
 3. Click **Regional Settings**.
 4. Choose your **Data Ingestion Region**.
     - If you're in the *US West* data processing region, you can select from: Dublin, Singapore, Oregon, and Sydney.
-    - If you're in the *EU West* data processing region, Segment's EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com/v1` endpoint.
+    - If you're in the *EU West* data processing region, Segment's EU instance only supports data ingestion from Dublin with the `events.eu1.segmentapis.com/` endpoint.
 
 All regions are configured on a **per-source** basis. You'll need to configure the region for each source separately if you don't want to use the default region.