Skip to content

Commit c04602c

Browse files
committed
Tiny text change
1 parent adbae07 commit c04602c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/Manual/Deployment/Kubernetes/DriverConfiguration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,10 +116,10 @@ follow-up request.
116116

117117
ArangoDB will transparently forward any mismatched requests to the correct
118118
coordinator, so the requests can be answered correctly without any additional
119-
configuration. However, this incurs a small performance penalty due to the extra
119+
configuration. However, this incurs a small latency penalty due to the extra
120120
request across the internal network.
121121

122-
To resolve this uncertainty client-side, make sure to run your client
122+
To prevent this uncertainty client-side, make sure to run your client
123123
application in the same Kubernetes cluster and synchronize your endpoints before
124124
making the initial query request. This will result in the use (by the driver) of
125125
internal DNS names of all coordinators. A follow-up request can then be sent to

0 commit comments

Comments
 (0)