summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2009-03-24 21:48:04 +0100
committerantirez <antirez@gmail.com>2009-03-24 21:48:04 +0100
commit4e4055779fc46370b2b1b99a0a2b1ff9cfc64013 (patch)
tree761694d4fbccd1e81bff330094d8edc92bc1272c /doc
parent43c9dc7bd273f39522119415318ec750e678748a (diff)
downloadredis-4e4055779fc46370b2b1b99a0a2b1ff9cfc64013.tar.gz
two typos fixed
Diffstat (limited to 'doc')
-rw-r--r--doc/ProtocolSpecification.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ProtocolSpecification.html b/doc/ProtocolSpecification.html
index 9551c6a58..955f286dc 100644
--- a/doc/ProtocolSpecification.html
+++ b/doc/ProtocolSpecification.html
@@ -29,7 +29,7 @@
<h1><a name="Protocol Specification">Protocol Specification</a></h1>The Redis protocol is a compromise between being easy to parse by a computer
and being easy to parse by an human. Before reading this section you are
strongly encouraged to read the &quot;REDIS TUTORIAL&quot; section of this README in order
-to get a first feeling of the protocol playing with it by TELNET.<h2><a name="Networking layer">Networking layer</a></h2>A client connects to a Redis server creating a TCP connection to the port 6973.
+to get a first feeling of the protocol playing with it by TELNET.<h2><a name="Networking layer">Networking layer</a></h2>A client connects to a Redis server creating a TCP connection to the port 6379.
Every redis command or data transmitted by the client and the server is
terminated by &quot;\r\n&quot; (CRLF).<h2><a name="Simple INLINE commands">Simple INLINE commands</a></h2>The simplest commands are the inline commands. This is an example of a
server/client chat (the server chat starts with S:, the client chat with C:)<br/><br/><pre class="codeblock python" name="code">