aboutsummaryrefslogtreecommitdiffstats
path: root/lib/inets/doc/src/http_client.xml
diff options
context:
space:
mode:
authorChristian von Roques <[email protected]>2010-12-15 17:36:09 -0400
committerNiclas Axelsson <[email protected]>2011-03-02 19:38:21 +0100
commit748dbeb1524122229373c5964334a8d8f18a525d (patch)
tree1d83be083538721e4cdb36fbfe7ced689a763be3 /lib/inets/doc/src/http_client.xml
parentf38a6085c5c65c9324b58e1e2fa8815093688f96 (diff)
downloadotp-748dbeb1524122229373c5964334a8d8f18a525d.tar.gz
otp-748dbeb1524122229373c5964334a8d8f18a525d.tar.bz2
otp-748dbeb1524122229373c5964334a8d8f18a525d.zip
inets/httpc: Polish documentation
* Assure store_cookies (and verify_cookies) is documented instead of the nonexistent store_cookie and verify_cookie. * Make sure the cookies option is not called cookie in comments. * Sprinkle <c>...</c> arround symbols and code snippets in text. * Grammar, wording, and punctuation fixes. * Formalize See gen_tcp:connect/3,4 using <seealso>.
Diffstat (limited to 'lib/inets/doc/src/http_client.xml')
-rw-r--r--lib/inets/doc/src/http_client.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/inets/doc/src/http_client.xml b/lib/inets/doc/src/http_client.xml
index 672ea3fa98..4542211d71 100644
--- a/lib/inets/doc/src/http_client.xml
+++ b/lib/inets/doc/src/http_client.xml
@@ -42,10 +42,10 @@
dynamically in runtime. Each client profile will spawn a new
process to handle each request unless there is a possibility to use
a persistent connection with or without pipelining.
- The client will add a host header and an empty
- te header if there are no such headers present in the request.</p>
+ The client will add a <c>host</c> header and an empty
+ <c>te</c> header if there are no such headers present in the request.</p>
- <p>The clients supports ipv6 as long as the underlying mechanisms also do
+ <p>The client supports ipv6 as long as the underlying mechanisms also do
so.</p>
</section>
@@ -87,7 +87,7 @@
httpc:request("http://www.erlang.org").
</code>
<p>An ordinary asynchronous request. The result will be sent
- to the calling process on the form {http, {ReqestId, Result}}</p>
+ to the calling process in the form <c>{http, {ReqestId, Result}}</c></p>
<code type="erl">
5 > {ok, RequestId} =
httpc:request(get, {"http://www.erlang.org", []}, [], [{sync, false}]).