Skip to content

Commit f4f2f9b

Browse files
author
Niall Brennan
committed
update proxy info
1 parent 7220d95 commit f4f2f9b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ When you successfully package a plugin in device-mode, you will no longer see th
8484
The instanceId was introduced in [V 1.10.1](https://github.com/segmentio/analytics-kotlin/releases/tag/1.10.1){:target="_blank"} and correlates events to a particular instance of the client in a scenario when you might have multiple instances on a single app.
8585

8686
## How should I configure my proxy URL?
87-
To proxy events to Segment's API, you can confiuge your proxy URL via the `requestFactory` setting:
87+
To proxy events to Segment's API, you can configure your proxy URL via the `requestFactory` setting:
8888
```
8989
Analytics(BuildConfig.SEGMENT_WRITE_KEY, androidContext()) {
9090
trackApplicationLifecycleEvents = true
@@ -104,4 +104,4 @@ Analytics(BuildConfig.SEGMENT_WRITE_KEY, androidContext()) {
104104
}
105105
```
106106

107-
If you proxy your events through the `apiHost` config option, you must forward the batched events to `https://api.segment.io/v1/b`. The `https://api.segment.io/v1/batch` endpoint is reserved for events arriving from server side sending, and proxying to that endpoint for your mobile events may result in unexpected behavior.
107+
When proxying your events, you must forward the batched events to `https://api.segment.io/v1/b`. The `https://api.segment.io/v1/batch` endpoint is reserved for events arriving from server side sending, and proxying to that endpoint for your mobile events may result in unexpected behavior.

0 commit comments

Comments
 (0)