Author: cutting
Date: Wed Mar 3 00:34:30 2010
New Revision: 918284
URL: http://svn.apache.org/viewvc?rev=918284&view=rev
Log:
AVRO-437. Fix some typos in docs. Contributed by Amichai Rothman.
Modified:
hadoop/avro/trunk/CHANGES.txt
hadoop/avro/trunk/doc/src/content/xdocs/index.xml
hadoop/avro/trunk/doc/src/content/xdocs/spec.xml
Modified: hadoop/avro/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/hadoop/avro/trunk/CHANGES.txt?rev=918284&r1=918283&r2=918284&view=diff
==============================================================================
--- hadoop/avro/trunk/CHANGES.txt (original)
+++ hadoop/avro/trunk/CHANGES.txt Wed Mar 3 00:34:30 2010
@@ -15,6 +15,8 @@
AVRO-431. Fix Java's mvn-install Ant target to work in clean build.
(cutting)
+ AVRO-437. Fix some typos in docs. (Amichai Rothman via cutting)
+
Avro 1.3.0 (24 February 2010)
INCOMPATIBLE CHANGES
Modified: hadoop/avro/trunk/doc/src/content/xdocs/index.xml
URL:
http://svn.apache.org/viewvc/hadoop/avro/trunk/doc/src/content/xdocs/index.xml?rev=918284&r1=918283&r2=918284&view=diff
==============================================================================
--- hadoop/avro/trunk/doc/src/content/xdocs/index.xml (original)
+++ hadoop/avro/trunk/doc/src/content/xdocs/index.xml Wed Mar 3 00:34:30 2010
@@ -56,7 +56,7 @@
schema, correspondence between same named fields, missing
fields, extra fields, etc. can all be easily resolved.</p>
<p>Avro schemas are defined with
- with <a href="http://www.json.org/";>JSON</a> . This
+ <a href="http://www.json.org/";>JSON</a> . This
facilitates implementation in languages that already have
JSON libraries.</p>
</section>
Modified: hadoop/avro/trunk/doc/src/content/xdocs/spec.xml
URL:
http://svn.apache.org/viewvc/hadoop/avro/trunk/doc/src/content/xdocs/spec.xml?rev=918284&r1=918283&r2=918284&view=diff
==============================================================================
--- hadoop/avro/trunk/doc/src/content/xdocs/spec.xml (original)
+++ hadoop/avro/trunk/doc/src/content/xdocs/spec.xml Wed Mar 3 00:34:30 2010
@@ -257,7 +257,7 @@
fullname <code>org.foo.X</code>.</li>
<li>A name only is specified, i.e., a name that contains no
dots. In this case the namespace is taken from the most
- tightly encosing schema or protocol. For example,
+ tightly enclosing schema or protocol. For example,
if <code>"name": "X"</code> is specified, and this occurs
within a field of the record definition
of <code>org.foo.Y</code>, then the fullname
@@ -911,7 +911,7 @@
<p>In this case the client must then re-submit its request
with its protocol text (<code>clientHash!=null,
clientProtocol!=null, serverHash!=null</code>) and the
- server should respond with with a successful match
+ server should respond with a successful match
(<code>match=BOTH, serverProtocol=null,
serverHash=null</code>) as above.</p>
</li>
