aboutsummaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2016-01-25 11:11:29 +0100
committerDaniel Stenberg <daniel@haxx.se>2016-01-25 11:11:29 +0100
commit14f92f2d2ce4106f65b3826a395b8450748758ab (patch)
tree0008e435fe0923701bc7a14f07a9e3f9e051b961 /docs/FAQ
parent53d1e42c41e15171387a17bd5ad178c7d249007f (diff)
FAQ: language fix in 4.19
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 706ac5e59..6f73eeb3d 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -1092,7 +1092,7 @@ FAQ
In such cases, the TCP/IP stack is responsible for detecting when the
network connection is irrevocably lost. Since with some protocols it is
- perfectly legal for the client wait indefinitely for data, the stack may
+ perfectly legal for the client to wait indefinitely for data, the stack may
never report a problem, and even when it does, it can take up to 20 minutes
for it to detect an issue. The curl option --keepalive-time enables
keep-alive support in the TCP/IP stack which makes it periodically probe the