Merge in documentation updates.

[m6w6/libmemcached] / docs / man / memcached_replace_by_key.3

diff --git a/docs/man/memcached_replace_by_key.3 b/docs/man/memcached_replace_by_key.3
index 4da65c83437156463380b44f3c25a4391cd40557..ec1ae4b42efef3a0604cfb780d1def9d9af041bb 100644 (file)
--- a/docs/man/memcached_replace_by_key.3
+++ b/docs/man/memcached_replace_by_key.3
@@ -139,7 +139,7 @@ memcached_set(), memcached_add(), and memcached_replace() are all used to
 store information on the server. All methods take a key, and its length to
 store the object. Keys are currently limited to 250 characters by the
 memcached(1) server. You must also supply a value and a length. Optionally you
-may support an expiration time for the object and a 16 byte value (it is
+may tests an expiration time for the object and a 16 byte value (it is
 meant to be used as a bitmap).
 .sp
 memcached_set() will write an object to the server. If an object already
@@ -162,7 +162,7 @@ data stored. Currently expiration and key are not used in the server.
 memcached_cas() overwrites data in the server as long as the "cas" value is
 still the same in the server. You can get the cas value of a result by
 calling memcached_result_cas() on a memcached_result_st(3) structure. At the point
-that this note was written cas is still buggy in memached. Turning on support
+that this note was written cas is still buggy in memached. Turning on tests
 for it in libmemcached(3) is optional. Please see memcached_set() for
 information on how to do this.
 .sp
@@ -175,7 +175,7 @@ objects to particular servers.
 If you are looking for performance, memcached_set() with non\-blocking IO is
 the fastest way to store data on the server.
 .sp
-All of the above functions are supported with the \fBMEMCACHED_BEHAVIOR_USE_UDP\fPbehavior enabled. But when using these operations with this behavior on, there
+All of the above functions are testsed with the \fBMEMCACHED_BEHAVIOR_USE_UDP\fPbehavior enabled. But when using these operations with this behavior on, there
 are limits to the size of the payload being sent to the server.  The reason for
 these limits is that the Memcahed Server does not allow multi\-datagram requests
 and the current server implementation sets a datagram size to 1400 bytes. Due
@@ -201,9 +201,6 @@ legitmate error in the case of a collision.
 .sp
 To find out more information please check:
 \fI\%https://launchpad.net/libmemcached\fP
-.SH AUTHOR
-.sp
-Brian Aker, <\fI\%brian@tangent.org\fP>
 .SH SEE ALSO
 .sp
 memcached(1) libmemached(3) memcached_strerror(3)