fix small typos

doc/generic/pgfplots/README

@@ -83,9 +83,9 @@ UNSTABLE:
 	in fact, some of the documented positions for 'xtick pos' where
 	unavailable.
 - fixed bug 155 [groupplots] `scaled ticks` does not recognize `ticklabels at` 
-- fixed bug 160 `xticklabels` also used for `extra x tick labels` if they are not given explicitely 
+- fixed bug 160 `xticklabels` also used for `extra x tick labels` if they are not given explicitly 
 - implemented partial solution for bug 154 [log mode] sampling in 2D and 3D different 
-- fixed bug 163 [bar-chart] bars dissapear when values are >xmax/ymax 
+- fixed bug 163 [bar-chart] bars disappear when values are >xmax/ymax 
 - fixed bug 81 cannot use dollar sign as 'comment char'
 - fixed bug 91 Hashes in data 
 - fixed bug 165 [minor ticks] minor tick drawn after the last xtick
@@ -109,7 +109,7 @@ UNSTABLE:
 - fixed bug: \usepgfplotslibrary{colorbrewer}: colormap 'PuOr' was defined in reverse order
 
 1.13:
-- fixed bug: incompatiblity between fillbetween and babel
+- fixed bug: incompatibility between fillbetween and babel
 - fixed bug: 'compat=1.9' (or newer) failed to work with log bar plots
 - fixed bug: javascript incompatibility between Acrobat reader DC and clickable lib
 - fixed bug in polar axes: repaired default axis label positions

doc/latex/pgfplots/TeX-programming-notes.tex

@@ -1060,7 +1060,7 @@ \subsection{The Low--Level (Direct) \API\ of \PGF Keys}
 \begin{commandlist}{%
 	\pgfkeysifdefined\marg{/key path/key name}\marg{true case}\marg{false case},
 	\pgfkeysifassignable\marg{/key path/key name}\marg{true case}\marg{false case}}
-	These keys provide conditionals based on existance or type of a key. Please refer to the reference manual in~\cite{tikz} for details.
+	These keys provide conditionals based on existence or type of a key. Please refer to the reference manual in~\cite{tikz} for details.
 \end{commandlist}
 
 \subsection{The Standard \API\ of \PGF Keys}

doc/latex/pgfplots/pgfplots.basic.reference.tex

@@ -531,7 +531,7 @@ \section{Specifying Basic Coordinates}
     Note that \PGFPlots{} substitutes |\pgfqpointxy| by |\pgfplotspointaxisxyz|
     by default -- and this command implicitly transforms coordinates anyway. In
     order to see the difference, the preceding example first disables this
-    automatic substition of coordinate systems by means of
+    automatic substitution of coordinate systems by means of
     |compat/pgfpoint substitution=1.3|.
     %
     The result of this command is also available as math method
@@ -734,7 +734,7 @@ \section{Accessing Point Coordinate Values}
 
 \begin{commandlist}{\pgfplotspointgetcoordinates,\pgfplotspointgetcoordinates\marg{point}}
 
-    After invoking the macro, the followings keys will be set:
+    After invoking the macro, the following keys will be set:
 
     \declaretext{/data point/x} will contain the current point's $x$-coordinate.
 

doc/latex/pgfplots/pgfplots.install.tex

@@ -232,7 +232,7 @@ \subsection{Restrictions for DVI Viewers and \texttt{dvipdfm}}
 \end{itemize}
 %
 However, there are some restrictions: I don't know any DVI viewer which is
-capable of viewing the output of \PGF{} (and therefor \PGFPlots{} as well).
+capable of viewing the output of \PGF{} (and therefore \PGFPlots{} as well).
 After all, DVI has never been designed to draw something different than text
 and horizontal/vertical lines. You will need to view the postscript file or the
 PDF file.

doc/latex/pgfplots/pgfplots.libs.patchplots.tex

@@ -937,7 +937,7 @@ \subsection{Automatic Patch Refinement and Triangulation}
 
     The refined patches reproduce the geometry's shape exactly. In addition,
     they improve color interpolation. Note that its purpose is just
-    visualization, therefor hanging nodes are allowed (and will be generated by
+    visualization, therefore hanging nodes are allowed (and will be generated by
     |patch refines| for most |patch type|s).
 
     Patch refinement is implemented for all supported patches except for

doc/latex/pgfplots/pgfplots.libs.statistics.tex

@@ -224,7 +224,7 @@ \subsubsection{Prepared Box Plots and Common Options}
     plot has |draw position=5| and is drawn at $x=5$.
 
     Note that if you assign |draw position| for one plot, you may also need to
-    adopt all followings ones as \PGFPlots{} does not automatically detect
+    adopt all following ones as \PGFPlots{} does not automatically detect
     collisions.
 \end{pgfplotskey}
 

doc/latex/pgfplots/pgfplots.reference.2dplots.tex

@@ -1249,7 +1249,7 @@ \subsection{Stacked Plots}
     stacked on top of each other and they are processed in the order of
     appearance. Then, the second plot could easily draw its lines (or fill
     area) on top of the first one -- hiding its marker or line completely.
-    Therefor, \PGFPlots{} reverses the sequence of drawing commands.
+    Therefore, \PGFPlots{} reverses the sequence of drawing commands.
 
     This has the side-effect that any normal \Tikz{} paths inside of an axis
     will also be processed in reverse sequence.

doc/latex/pgfplots/pgfplots.reference.axis-addplot.tex

@@ -2191,7 +2191,7 @@ \subsection*{Support for External Three-Dimensional Graphics}
 This is due to the |scale mode=scale uniformly| implementation of \PGFPlots{}:
 it decided that the best way is to enlarge the involved axis limits. Here,
 ``best way'' means to satisfy |width|/|height| constraints combined with
-minimally enlarged (never shrinked) axis limits. The remaining degrees of
+minimally enlarged (never shrunk) axis limits. The remaining degrees of
 freedom are |width|, |height|, and the axis limits. In our case, changing the
 ratio between |width| and |height| improves the display:
 
@@ -2358,7 +2358,7 @@ \subsection*{External Three-Dimensional Graphics and Matlab}
 pos = get(event_obj,'Position');
 
 % Format the data and figure coordinates. The factor "72.27/dpi" is
-% necessary to convert from pixels to TeX points (72.27 poins per inch)
+% necessary to convert from pixels to TeX points (72.27 points per inch)
 display(['(',num2str(pos(1)),',',num2str(pos(2)),',',num2str(pos(3)),') => (', ...
    num2str((screen_location(1)-figurePos(1))*72.27/dpi),',', ...
    num2str((screen_location(2)-figurePos(2))*72.27/dpi),')'])

doc/latex/pgfplots/pgfplots.reference.bb-clip.tex

@@ -266,7 +266,7 @@ \subsection{Clipping}
 
     Note that a clip path can contribute to the picture's bounding box.
     Starting with |compat=1.8|, \PGFPlots{} applies intelligence to separate
-    the responsabilities clipping and bounding box control, see
+    the responsibilities clipping and bounding box control, see
     |clip bounding box| and its choices. As of |compat=1.8|, a clip path can be
     in effect although the bounding box is considerably smaller than the clip
     path. This is typically what one expects if the clip path is invisible.

doc/latex/pgfplots/pgfplots.reference.symbolic-transformations.tex

@@ -257,7 +257,7 @@ \subsection{Dates as Input Coordinates}
     contain stuff like |hist/data|.
 
     After installing this style, input values like |2006-02-28| will be
-    converted to an ``appropriate'' integer using the Julian calender. Input
+    converted to an ``appropriate'' integer using the Julian calendar. Input
     coordinates may be of the form
 
         \meta{year}|-|\meta{month}|-|\meta{day}

source/context/third/pgfplots/pgfplotstest/pgfplotstest.ticks.tex

@@ -145,7 +145,7 @@
 \stopaxis
 \stoptikzpicture
 
-\testsection{Tick label assigment tests}
+\testsection{Tick label assignment tests}
 \testsubsection{Using xticklabel and xtick}
 \starttikzpicture
 \startaxis[

source/latex/pgfplots/numtabletest/numtabletest.tex

@@ -40,19 +40,19 @@
 \pgfplotstableread{numtabletestdata}\table
 \tracingmacros=0\tracingcommands=0
 
-\testsubsection{Quering colnames...}
+\testsubsection{Querying colnames...}
 %\tracingmacros=2\tracingcommands=2
 \pgfplotstablegetcolumnlist\table\to\cols
 \pgfplotslistforeach\cols\as\col{Column ``\col''\par}%
 %\tracingmacros=0\tracingcommands=0
 
-\testsubsection{Quering column content by column name}
+\testsubsection{Querying column content by column name}
 %\tracingmacros=2\tracingcommands=2
 \pgfplotstablegetcolumnbyname L2\of\table\to\colcontent
 \pgfplotslistforeach\colcontent\as\colc{Row data: ``\colc''\par}%
 %\tracingmacros=0\tracingcommands=0
 
-\testsubsection{Quering column content by column name for all cols}
+\testsubsection{Querying column content by column name for all cols}
 \pgfplotstablegetcolumnlist\table\to\cols
 \pgfplotslistforeach\cols\as\col{\textbf{Column ``\col''}\par
 	\pgfplotstablegetcolumnbyname\col\of\table\to\colcontent
@@ -65,7 +65,7 @@
 \pgfplotstableread{numtabletestdata2.gnuplot}\table
 %\tracingmacros=0\tracingcommands=0
 
-\testsubsection{Quering column content by column name for all cols}
+\testsubsection{Querying column content by column name for all cols}
 \pgfplotstablegetcolumnlist\table\to\cols
 \pgfplotslistforeach\cols\as\col{\textbf{Column ``\col''}\par
 	\pgfplotstablegetcolumnbyname\col\of\table\to\colcontent

source/latex/pgfplots/pgfplotstest/regressiontests/Makefile

@@ -154,7 +154,7 @@ cleanX:
 	@# touch diff.png in case the diff routine fails -- we want to see it in the error report counts
 	@./pdfdiff.sh $< references/$< $@ || touch $@.png
 	@if [ "`cat $@`" = "0 (0)" ]; then \
-		echo "  PASSED: no differences detected (removing superfluos diff-pngs)"; \
+		echo "  PASSED: no differences detected (removing superfluous diff-pngs)"; \
 		rm -f $@.png $<.png $(DIRECTORY_FOR_ACCEPTED_ERRORS)/$@ $(DIRECTORY_FOR_ACCEPTED_ERRORS)/$@.png; # no need to keep the images (the latter for multi-page mode). \
 	else \
 		#echo "$<: found nonzero pixel differences `cat $@`."; \
@@ -171,7 +171,7 @@ cleanX:
 		rm -f $@.normalized; \
 		calc -p "$$NORMALIZED <= $$ACCEPTED_ERROR" > $@.isaccepted || ( echo "calc invocation failed. Please ensure that apcalc package is installed."; exit 1 ); \
 		if [ "`cat $@.isaccepted`" = "1" ]; then \
-			echo "  PASSED: only approved differences $$NORMALIZED <= $$ACCEPTED_ERROR detected; moving superfluos diff-pngs to $(DIRECTORY_FOR_ACCEPTED_ERRORS))"; \
+			echo "  PASSED: only approved differences $$NORMALIZED <= $$ACCEPTED_ERROR detected; moving superfluous diff-pngs to $(DIRECTORY_FOR_ACCEPTED_ERRORS))"; \
 			mkdir -p $(DIRECTORY_FOR_ACCEPTED_ERRORS); \
 			mv $@.png $(DIRECTORY_FOR_ACCEPTED_ERRORS); \
 			cp $@ $(DIRECTORY_FOR_ACCEPTED_ERRORS); \

source/latex/pgfplots/pgfplotstest/regressiontests/patchplots/patch_plot_example.m

@@ -33,7 +33,7 @@
 print('plot1.png','-dpng');
 patchtopgfplots(tx,ty,[], tcm, 'plot1.dat');
 
-% Second type, interpolated colors, seperate for each patch
+% Second type, interpolated colors, separate for each patch
 close all
 patch(tx',ty',c2');
 print('plot2.png','-dpng');

source/latex/pgfplots/pgfplotstest/regressiontests/unittest_libs_patchplots_matlab.tex

@@ -59,7 +59,7 @@ \subsection{Interpolated colors, separate for each patch}
 	\end{axis}
 \end{tikzpicture}
 
-\subsection{Interpolated colors, continous over edges}
+\subsection{Interpolated colors, continuous over edges}
 Matlab:
 
 \matlabtestimg{plot3.png}

source/latex/pgfplots/pgfplotstest/unittest/unittest_colorinput_sanitize.tex

@@ -15,13 +15,13 @@
 \pgfplotscolornormalizesequence[colorspace=rgb]
 
 \pgfplotscolornormalizesequencenext{rgb255=-1,0,0}
-\pgfplotsassertequalstok{Sorry, the color component value -0.00392 (no. 0) is out of range. The allowed range is 0 <= value <= 1. The error occured near `rgb255=-1,0,0'}{\pgfplotsERRORMESSAGE}{}%
+\pgfplotsassertequalstok{Sorry, the color component value -0.00392 (no. 0) is out of range. The allowed range is 0 <= value <= 1. The error occurred near `rgb255=-1,0,0'}{\pgfplotsERRORMESSAGE}{}%
 
 \def\pgfplotsERRORMESSAGE{}
 
 % FAILS UTTERLY: confused with 'gray=...' : \pgfplotscolornormalizesequencenext{green}
 \pgfplotscolornormalizesequencenext{blue}
-\pgfplotsassertequalstok{Sorry, the color component value 'blue' is no number. Did you mean 'color=blue'? The error occured near `blue'}{\pgfplotsERRORMESSAGE}{}%
+\pgfplotsassertequalstok{Sorry, the color component value 'blue' is no number. Did you mean 'color=blue'? The error occurred near `blue'}{\pgfplotsERRORMESSAGE}{}%
 
 
 
@@ -35,5 +35,5 @@
     	{[1cm] rgb255(0cm)=(25,25,122) color(1cm)=(yellow) rgb255(5cm)=(238,1140,238)}
 }
 
-	\pgfplotsassertequalstok{Sorry, the color component value 4.47052000000000 (no. 1) is out of range. The allowed range is 0 <= value <= 1. The error occured near `rgb255(5cm)=(238,1140,238) (color no 2)\space\space(color no 2) '}{\pgfplotsERRORMESSAGE}{}%
+	\pgfplotsassertequalstok{Sorry, the color component value 4.47052000000000 (no. 1) is out of range. The allowed range is 0 <= value <= 1. The error occurred near `rgb255(5cm)=(238,1140,238) (color no 2)\space\space(color no 2) '}{\pgfplotsERRORMESSAGE}{}%
 \end{document}

tex/generic/pgfplots/libs/pgfplotslibrary.code.tex

@@ -62,7 +62,7 @@
 
 \pgfkeys{
 	% #1: library name
-	% #2: compatiblity presets which are controlled by the
+	% #2: compatibility presets which are controlled by the
 	% compatibility system but which belong to the library.
 	%
 	% FIXME : now as I wrote it, it might have been better to reverse

tex/generic/pgfplots/libs/tikzlibrarypgfplots.smithchart.code.tex

@@ -49,7 +49,7 @@
 %
 % Idea: 
 %   - work on H
-%   - transform whereever necessary
+%   - transform wherever necessary
 %   - implement all pgfplots wrinkles in analogy to polar axes
 %   - provide support for normalized input coords (combined with
 %   untransformed limits or something like that)

tex/generic/pgfplots/liststructure/pgfplotsarray.code.tex

@@ -662,7 +662,7 @@
 	\pgfplotsarrayinsertionsort@@next
 }%
 
-% applies a binary seach for value '#2' on array '#1', starting with
+% applies a binary search for value '#2' on array '#1', starting with
 % index '#3' (inclusive) and ending in index '#4' (exclusive).
 %
 % Returns: \pgfplotsretval, the index of the search key, if it is

tex/generic/pgfplots/liststructure/pgfplotsliststructureext.code.tex

@@ -29,7 +29,7 @@
 % to its generality. It could easily be adopted to be FASTER than
 % \pgfplotsapplist.
 %
-% Credits for \pgfplotsapplist go to Till Tantau: he developped it for
+% Credits for \pgfplotsapplist go to Till Tantau: he developed it for
 % the PGF kernel.
 %
 %

tex/generic/pgfplots/lua/pgfplotsoldpgfsupp/luamath/functions.lua

@@ -500,7 +500,7 @@ end
 function pgfluamathfunctions.pointnormalised (pgfx, pgfy)
    local pgfx_normalised, pgfy_normalised
    if pgfx == 0. and pgfy == 0. then
-      -- Orginal pgf macro gives this result
+      -- Original pgf macro gives this result
       tex.dimen['pgf@x'] = "0pt"
       tex.dimen['pgf@y'] = "1pt"
    else

tex/generic/pgfplots/numtable/pgfplotstable.code.tex

@@ -147,7 +147,7 @@
 				\else
 					\pgfutil@ifundefined{pgfplotstable@unique@bitlist@backup}{%
 						% this sanity checking is NOT fool proof: it
-						% fails if there are different occurances of
+						% fails if there are different occurrences of
 						% unique in the same file
 						\pgfplotsthrow{invalid argument}{Sorry, the row predicate /pgfplots/table/unique={#1} has been used in the wrong context: it needs to be invoked for the very first processed column, not column no \pgfplotstablecol. Please provide it as argument to \string\pgfplotstabletypeset[unique={#1}] and not inside of column-specific styles}\pgfeov%
 					}{}%
@@ -1181,7 +1181,7 @@
 	}%
 	\pgfkeysgetvalue{/pgfplots/table/columns}{\pgfplotstable@colnames}%
 	\ifx\pgfplotstable@colnames\pgfutil@empty
-		\pgfplots@warning{\string\pgfplotstablenew[columns={},...]{#2}{\string#3} has been invoked - but empty tables are currently not really supported, sorry. You will have to live with an artifical column which contains temporary values.}%
+		\pgfplots@warning{\string\pgfplotstablenew[columns={},...]{#2}{\string#3} has been invoked - but empty tables are currently not really supported, sorry. You will have to live with an artificial column which contains temporary values.}%
 	\else
 		\expandafter\pgfplots@assign@list\expandafter\pgfplotstablenew@cols\expandafter{\pgfplotstable@colnames}%
 		% make sure every requested column exists:
@@ -1316,7 +1316,7 @@
 % <options>, see the declaration above.
 %
 % ATTENTION: the default implementation employs
-% \begin{tabular}...\end{tabular} and is therefor only usable with
+% \begin{tabular}...\end{tabular} and is therefore only usable with
 % LaTeX!
 %
 % You will need to reconfigure the tables.
@@ -1614,7 +1614,7 @@
 % \pgfplots@each@nth@styles.
 \def\pgfplotstabletypeset@append@every@nth@row#1#2{%
 	\edef\pgfplots@loc@TMPa{#1}%
-	% chech for the special 'each nth row={3[+1]}{...} format:
+	% check for the special 'each nth row={3[+1]}{...} format:
 	\expandafter\pgfutil@in@\expandafter[\expandafter{\pgfplots@loc@TMPa}%
 	\ifpgfutil@in@
 		\expandafter\pgfplotstabletypeset@append@every@nth@row@getshift\pgfplots@loc@TMPa%
@@ -1815,7 +1815,7 @@
 		% as the number of *output* rows (see the row predicate
 		% below).
 		%
-		% Accessable with \pgfplotstablerows in style keys.
+		% Accessible with \pgfplotstablerows in style keys.
 		\ifnum\c@pgfplotstable@numrows=-1\relax
 			\pgfplotslistsize\pgfplotstable@col\to\c@pgfplotstable@numrows
 			\global\c@pgfplotstable@numrows=\c@pgfplotstable@numrows
@@ -3008,7 +3008,7 @@
 	% '\pgfp@tmp@<index>'. Thus, column names and array indices are
 	% essentially the same! That simplifies the operation and explains
 	% why we transposed the table.
-	% We simply interprete the transposed table as array. We don't
+	% We simply interpret the transposed table as array. We don't
 	% even need to copy anything.
 	\pgfplotsarrayresize{\pgfp@tmp}{\pgfplotstable@numrows}%
 	% Oh, we also need the index to access the sort key. Well, then we

tex/generic/pgfplots/numtable/pgfplotstableshared.code.tex

@@ -2,7 +2,7 @@
 %
 % Package pgfplotstable
 %
-% Provides support to read and work with abstact numeric tables of the
+% Provides support to read and work with abstract numeric tables of the
 % form
 %
 % COLUMN1	COLUMN2 COLUMN3
@@ -324,7 +324,7 @@
 	\fi
 }%
 
-% If the colum name `#1' is a `create on use' speicifcation, #2 is
+% If the column name `#1' is a `create on use' speicifcation, #2 is
 % invoked, #3 otherwise.
 \long\def\pgfplotstableifiscreateonuse#1#2#3{%
 	\pgfkeysifdefined{/pgfplots/table/create on use/#1/.@cmd}{#2}{%
@@ -379,7 +379,7 @@
 		% Checks if column '#1' exists in table `#2' and invokes `#3' if that
 		% is the case and `#4' if not.
 		%
-		% Note that the check is only for physically existent colums, no alias
+		% Note that the check is only for physically existent columns, no alias
 		% or create on use is checked here.
 		% #1: colname
 		% #2: table struct
@@ -1810,7 +1810,7 @@
 	\pgfutil@ifundefined{pgfplotstableread@impl@COLNAME@#1}{%
 		\def\pgfplotstable@loc@TMPa{#1}%
 	}{% generate unique column names warning:
-		\pgfplots@warning{Table '\pgfplotstableread@filename' has non-unique column name '#1'. Only the first occurence can be accessed via column names.}%
+		\pgfplots@warning{Table '\pgfplotstableread@filename' has non-unique column name '#1'. Only the first occurrence can be accessed via column names.}%
 		\edef\pgfplotstable@loc@TMPa{#1--index\thepgfplotstableread@curcol}%
 	}%
 	\expandafter\def\csname pgfplotstableread@impl@COLNAME@#1\endcsname{foo}% remember this name.
@@ -1979,7 +1979,7 @@
 % which \catcodes need to be adjusted -- and <options> might explain
 % how.
 %
-% REMARK: An early attempt to change the precendence for 'every table'
+% REMARK: An early attempt to change the precedence for 'every table'
 % was to set <options> again after 'every table'. But that is
 % incompatible with, for example '/.add={}{}' key handlers.
 %