[Rprotobuf-commits] r806 - papers/jss

[noreply at r-forge.r-project.org]

Author: murray
Date: 2014-01-21 06:42:31 +0100 (Tue, 21 Jan 2014)
New Revision: 806

Modified:
   papers/jss/article.Rnw
Log:
spellcheck.



Modified: papers/jss/article.Rnw
===================================================================
--- papers/jss/article.Rnw	2014-01-21 05:37:30 UTC (rev 805)
+++ papers/jss/article.Rnw	2014-01-21 05:42:31 UTC (rev 806)
@@ -161,18 +161,18 @@
 environment.  
 
 %\paragraph*{Friends don't let friends use CSV!}
-Data analysts and researchers often use character seperated text formats such
+Data analysts and researchers often use character separated text formats such
 as \texttt{CSV} \citep{shafranovich2005common} to export and import
 data. However, anyone who has ever used \texttt{CSV} files will have noticed
 that this method has many limitations: it is restricted to tabular data,
 lacks type-safety, and has limited precision for numeric values.  Moreover,
 ambiguities in the format itself frequently cause problems.  For example,
-conventions on which characters is used as seperator or decimal point vary by
+conventions on which characters is used as separator or decimal point vary by
 country.  \emph{Extensible Markup Language} (\texttt{XML}) is another
 well-established and widely-supported format with the ability to define just
 about any arbitrarily complex schema \citep{nolan2013xml}. However, it pays
 for this complexity with comparatively large and verbose messages, and added
-complexitiy at the parsing side (which are somewhat mitigated by the
+complexity at the parsing side (which are somewhat mitigated by the
 availability of mature libraries and parsers). Because \texttt{XML} is text
 based and has no native notion of numeric types or arrays, it usually not a
 very practical format to store numeric datasets as they appear in statistical
@@ -1266,7 +1266,7 @@
 \ref{rexp.proto}. The Protocol Buffer messages generated by \pkg{RProtoBuf} and
 \pkg{RHIPE} are naturally compatible between the two systems because they use the 
 same schema. This shows the power of using a schema based cross-platform format such
-as Protocol Buffers: interoperability is archieved without effort or close coordination.
+as Protocol Buffers: interoperability is achieved without effort or close coordination.
 
 The \texttt{rexp.proto} schema supports all main R storage types holding \emph{data}.
 These include \texttt{NULL}, \texttt{list} and vectors of type \texttt{logical},