docs: sanitize

[awesomized/libmemcached] / docs / source / libmemcached / memcached_set.rst

diff --git a/docs/source/libmemcached/memcached_set.rst b/docs/source/libmemcached/memcached_set.rst
index dc044d592db706b8875199391eaec0cb4dcb8c50..3daf5b6b35a3eea339b94227f4ecb9ec4496b8ed 100644 (file)
--- a/docs/source/libmemcached/memcached_set.rst
+++ b/docs/source/libmemcached/memcached_set.rst
@@ -3,7 +3,6 @@ Storing data on the server
 
 .. index:: object: memcached_st
 
---------
 SYNOPSIS
 --------
 
@@ -22,7 +21,6 @@ SYNOPSIS
 
 .. function:: memcached_return_t memcached_replace_by_key(memcached_st *ptr, const char *group_key, size_t group_key_length, const char *key, size_t key_length, const char *value, size_t value_length, time_t expiration, uint32_t flags)
 
------------
 DESCRIPTION
 -----------
 
@@ -31,7 +29,7 @@ store the object. Keys are currently limited to 250 characters by the
 memcached(1) server. You must supply both a value and a length. Optionally you
 may test an expiration time for the object and a 16 byte value (it is meant to be used as a bitmap). "flags" is a 4byte space that is stored alongside of the main value. Many sub libraries make use of this field, so in most cases users should avoid making use of it.
 
-:func:`memcached_set` will write an object to the server. If an object 
+:func:`memcached_set` will write an object to the server. If an object
 already exists it will overwrite what is in the server. If the object does not 
 exist it will be written. If you are using the non-blocking mode this function
 will always return true unless a network error occurs.