Merge pull request #1336 from mbertucci47/typos

fix small typos

doc/generic/pgf/pgfmanual-en-dv-visualizers.tex

@@ -740,7 +740,7 @@ \subsection{Advanced: Creating New Visualizers}
 Now, let's see how this works:
 
 % TODOsp: codeexamples: This stuff is all needed for the next `codeexample`
-%         but cannot be stored (simply) in `setup code`, `preample` or `pre`
+%         but cannot be stored (simply) in `setup code`, `preamble` or `pre`
 \pgfooclass{circle visualizer} {
   % Stores the name of the visualizer. This is needed for filtering
   % and configuration

doc/generic/pgf/pgfmanual-en-gd-algorithms-in-c.tex

@@ -755,7 +755,7 @@ \subsubsection{The Hello World of Graph Drawing in OGDF -- Adapting Existing Cla
 // File HelloWorldLayout.h
 #include <ogdf/module/LayoutModule.h>
 
-class HelloWorldLayout : puplic ogdf::LayoutModule {
+class HelloWorldLayout : public ogdf::LayoutModule {
 public:
 
   virtual void call(ogdf::GraphAttributes &GA)

doc/generic/pgf/pgfmanual-en-pgfsys-commands.tex

@@ -460,7 +460,7 @@ \subsection{Graphic State Option System Commands}
 \end{command}
 
 \begin{command}{\pgfsys@setdash\marg{pattern}\marg{phase}}
-    Sets the dashing patter. \meta{pattern} should be a list of \TeX\
+    Sets the dashing pattern. \meta{pattern} should be a list of \TeX\
     dimensions separated by commas. \meta{phase} should be a single dimension.
 
     \example |\pgfsys@setdash{3pt,3pt}{0pt}|
@@ -645,7 +645,7 @@ \subsection{Pattern System Commands}
     This command declares a new colored or uncolored pattern, depending on
     whether \meta{flag} is |0|, which means uncolored, or |1|, which means
     colored. Uncolored patterns have no inherent color, the color is provided
-    when they are set. Colored patters have an inherent color.
+    when they are set. Colored patterns have an inherent color.
 
     The \meta{name} is a name for later use when the pattern is to be shown.
     The pairs $(x_1,y_1)$ and $(x_2,y_2)$ must describe a bounding box of the

source/generic/pgf/c/graphdrawing/pgf/gd/examples/c/SimpleDemoC.c

@@ -25,7 +25,7 @@ int luaopen_pgf_gd_examples_c_SimpleDemoC (struct lua_State *state) {
      the nodes of a graph in a circle (without paying heed to the sizes of the \
      nodes or to the edges). Its main purpose is to show how C code	\
      can access the Lua representation of graphs. See \
-     Section~\ref{section-algorithms-in-c} of the manual for detais.");
+     Section~\ref{section-algorithms-in-c} of the manual for details.");
   pgfgd_key_add_precondition (d, "connected");
   pgfgd_declare              (state, d);
   pgfgd_free_key             (d);

source/generic/pgf/c/graphdrawing/pgf/gd/interface/c/InterfaceFromC.c

@@ -849,7 +849,7 @@ pgfgd_Edge_array* pgfgd_digraph_syntactic_edges  (pgfgd_Digraph* g, int tail, in
 {
   pgfgd_Edge_array* edges = (pgfgd_Edge_array*) calloc(1, sizeof(pgfgd_Edge_array));
 
-  // First, get the arc in the syntatic digraph.
+  // First, get the arc in the syntactic digraph.
   lua_State* L = g->state;
   int tos = lua_gettop(L);
 

source/generic/pgf/c/graphdrawing/pgf/gd/interface/c/InterfaceFromC.h

@@ -164,13 +164,13 @@ typedef struct pgfgd_Vertex {
 
   /** The pos field of the Lua Vertex class. Unlike the other fields
       of this struct, you can write pos.x and pos.y. When the graph
-      drawing function returns, the values stored in theses fields
+      drawing function returns, the values stored in these fields
       will be written back to the Lua layer.
   */
   pgfgd_Coordinate pos;
 
   /** The options fields of the Lua Vertex class. Note that you do
-      not have direct access to theses options. Rather, all access to
+      not have direct access to these options. Rather, all access to
       them must go through functions like pgfgd_isset that take a
       pgfgd_OptionsTable* as input. Also note that you cannot store a
       pointer to an options table: At the end of the graph drawing
@@ -297,7 +297,7 @@ typedef struct pgfgd_SyntacticDigraph {
   pgfgd_Vertex_array vertices;
 
   /** All syntactic edges of the graph. You cannot modify this array,
-      but you can use the pgfgd_path_xxx funtion to change the routing
+      but you can use the pgfgd_path_xxx function to change the routing
       of the edges stored here. Note that, since you get access to 
       syntactic edges, the direction of these edges may not be what
       you expect and there may be several syntactic edges between the
@@ -382,7 +382,7 @@ typedef struct pgfgd_Digraph pgfgd_Digraph;
     pgfgd_Vertex objects. The reason is that a pgfgd_Digraph may
     actually contain vertices that are not present in the syntactic
     digraph (for instance, dummy vertices in a spanning tree) and for
-    which no pgfgd_Vertex obejct exists. For this reason, we only use
+    which no pgfgd_Vertex object exists. For this reason, we only use
     indices and there is a special function
     (pgfgd_digraph_syntactic_vertex) that can be used to retrieve the
     pgfgd_Vertex object, provided it exists.
@@ -421,7 +421,7 @@ typedef struct pgfgd_Arc_array {
     store a |Digraph| object. Examples are "digraph" or "ugraph". The
     function will then return a handle to this digraph which you can
     subsequently access. The handle will become invalid at the end of
-    the graph drawing funciton and you must free it explicitly using
+    the graph drawing function and you must free it explicitly using
     pgfgd_digraph_free. 
  */
 extern pgfgd_Digraph*    pgfgd_get_digraph              (pgfgd_SyntacticDigraph* g, const char* graph_name);
@@ -438,13 +438,13 @@ extern int               pgfgd_digraph_num_vertices     (pgfgd_Digraph* g);
 */
 extern pgfgd_Arc_array*  pgfgd_digraph_arcs             (pgfgd_Digraph* g);
 
-/** This function allows you to retrieve the syntatic vertex that
+/** This function allows you to retrieve the syntactic vertex that
     corresponds to a given index in the digraph. Normally, the first
     vertex of a digraph like the ugraph will also be the first entry
     of the vertices field of the syntactic digraph, but this need not
     always be the case. For instance, for a spanning_tree digraph,
     there will be more vertices in the graph than there are syntactic
-    vertices and the order may be quite different. For theses reaons,
+    vertices and the order may be quite different. For these reasons,
     you must use this function to convert a vertex index into the
     digraph g into a pgfgd_Vertex object. It may happen that the index
     does not refer to any syntactic vertex, in this case 0 is
@@ -466,7 +466,7 @@ extern int               pgfgd_digraph_isarc            (pgfgd_Digraph* g, int t
     returned array explicitly using
     pgfgd_digraph_free_edge_array. Typically, this array will have at
     most one entry, but it may happen that the user has specified
-    several syntatic edges between the same vertices, in which case
+    several syntactic edges between the same vertices, in which case
     you get a larger array here.
 
     Note that tail and head are indices (starting with 1) into the
@@ -568,7 +568,7 @@ extern void pgfgd_key_phase             (pgfgd_Declaration* d, const char* s);
     some point, it would call the actual Lua graph drawing
     algorithm. At that point, the function f is called instead. The
     parameter of this function will be a representation of the
-    to-be-drawn syntatic digraph as a C pgfgd_SyntacticDigraph. 
+    to-be-drawn syntactic digraph as a C pgfgd_SyntacticDigraph. 
 */
 extern void pgfgd_key_algorithm         (pgfgd_Declaration* d,
 					 pgfgd_algorithm_fun f,

source/generic/pgf/testsuite/external/tikzexternaltest.code.tex

@@ -8,7 +8,7 @@
 \begin{tikzpicture}[baseline]
     \draw (0,0) grid (4,4);
 \end{tikzpicture}
-an explizit file name.
+an explicit file name.
 
 \begin{tikzpicture}
     \node[draw,rounded corners] {A node with a ref (\ref{eq:1})};

tex/generic/pgf/frontendlayer/tikz/libraries/tikzexternalshared.code.tex

@@ -310,7 +310,7 @@
     }%
 }%
 
-% Auto-select a suitable default value fo 'system call':
+% Auto-select a suitable default value for 'system call':
 \pgfutil@ifundefined{tikzexternal@driver@\pgfsysdriver}{%
     % fallback. We do not know the driver here.
     \csname tikzexternal@[email protected]\endcsname

tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryanimations.code.tex

@@ -296,7 +296,7 @@
 
 \def\tikz@anim@path@parse#1{%
   {%
-    \setbox0=\hbox{{% protext against side effects
+    \setbox0=\hbox{{% protect against side effects
         \pgfinterruptpath%
         \expandafter\tikz@scan@next@command#1\pgf@stop%
         \pgfsyssoftpath@getcurrentpath\tikz@anim@result%

tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryintersections.code.tex

@@ -53,7 +53,7 @@
   \expandafter\pgfutil@g@addto@macro\expandafter\tikz@intersect@namedpaths\expandafter{\tikz@marshal}%
 }%
 
-% at the end of evey \path command ...
+% at the end of every \path command ...
 \let\tikz@finish@orig=\tikz@finish
 \def\tikz@finish{%
   \tikz@finish@orig%

tex/generic/pgf/graphdrawing/lua/pgf/gd/force/ControlCoarsening.lua

@@ -57,7 +57,7 @@ declare {
     expected to be higher than graphics where this feature is not applied.
 
     The following example demonstrates how coarsening can improve the
-    quality of graph drawings generated with Walshaw's algorihtm
+    quality of graph drawings generated with Walshaw's algorithm
     |spring electrical layout'|.
   "]],
   examples = [["

tex/generic/pgf/graphdrawing/lua/pgf/gd/force/library.lua

@@ -43,7 +43,7 @@
 --   \item If the nodes are connected by an edge, one can treat the edge as
 --     a ``spring'' that has a ``natural spring dimension''. If the nodes
 --     are nearer than the spring dimension, they are push apart; if they
---     are farther aways than the spring dimension, they are pulled together.
+--     are farther away than the spring dimension, they are pulled together.
 --   \item If two nodes are connected by a path of a certain length, the
 --     nodes may ``wish to be at a distance proportional to the path
 --     length''. If they are nearer, they are pushed apart; if they are

tex/generic/pgf/graphdrawing/lua/pgf/gd/model/Path_arced.lua

@@ -171,7 +171,7 @@ local function arc (path, start, start_angle, end_angle, radius, trans, centerx,
     end_angle   = end_angle % 360
 
     if end_angle >= start_angle then
-      -- In case the modulo has inadvertedly moved the end angle
+      -- In case the modulo has inadvertently moved the end angle
       -- before the start angle:
       end_angle = end_angle - 360
     end

tex/generic/pgf/graphdrawing/lua/pgf/gd/trees/SpanningTreeComputation.lua

@@ -436,7 +436,7 @@ declare {
   },
 
   summary = [["
-    Assings a uniform priority of 5 to all edges.
+    Assigns a uniform priority of 5 to all edges.
   "]]
 }
 

tex/generic/pgf/graphdrawing/tex/pgflibrarygraphdrawing.code.tex

@@ -540,7 +540,7 @@
 % #2 = second node
 % #3 = edge direction
 % #4 = edge options (will be executed in a protected environment)
-% #5 = aux stuff (curtesy for TikZ -- edge nodes)
+% #5 = aux stuff (courtesy for TikZ -- edge nodes)
 %
 % Description:
 %
@@ -604,7 +604,7 @@
 %
 %
 % The text in #5 is some "auxiliary" text that is simply stored away
-% and later directly to \pgfgdcallbackedge. This is a curtesy to TikZ,
+% and later directly to \pgfgdcallbackedge. This is a courtesy to TikZ,
 % which can use it to store its node labels.
 %
 % Example:

tex/generic/pgf/modules/pgfmoduledatavisualization.code.tex

@@ -2721,7 +2721,7 @@
       %
       %
       % Compute the ideal number of entries per row/column (called
-      % "target" in the following) and entries per colum/row (called
+      % "target" in the following) and entries per column/row (called
       % "per target" in the following)
       %
       % if (number of entries > ideal)

tex/generic/pgf/systemlayer/pgfsys-tex4ht.def

@@ -115,7 +115,7 @@
         % okey
         padding:0;
         margin:0;
-        % background-color:\#12ff55;  usefull for debugging positioning
+        % background-color:\#12ff55;  useful for debugging positioning
         text-align:center; % good for centered text nodes...will have to improve that later on...with more integration with pgf options for text nodes
       }
     }%
@@ -179,7 +179,7 @@
   }%
   \pgfsys@invoke{<?xml version="1.0" encoding="iso-8859-1" standalone="no"?>\Hnewline% added that
   <?xml-stylesheet href="\pgfsys@foreignobject@css.css" type="text/css"?>\Hnewline}% added that
-%%%%%%%%%%%%%%% maybee I should add an option to change the css, for the whole picture
+%%%%%%%%%%%%%%% maybe I should add an option to change the css, for the whole picture
   \pgfsys@invoke{<svg xmlns="http://www.w3.org/2000/svg"
     xmlns:xlink="http://www.w3.org/1999/xlink" width="\the\pgf@xc"
     height="\the\pgf@yc" viewBox="}%
@@ -310,7 +310,7 @@
   \hbox to#2\bgroup
     \hsize=#2\relax
     \vbox\bgroup
-% though it works, I'm desabling the above-mentioned hack to make tex4ht behave with <p> <\p>, because it blurps the positioning
+% though it works, I'm disabling the above-mentioned hack to make tex4ht behave with <p> <\p>, because it blurps the positioning
 % (I''l try to fix that later, it's a css thing)
 %
 %    \ifpgfsys@textonly\else\HtmlParOn\fi
@@ -414,7 +414,7 @@
 
 % There is something rellay wrong with the way "%" chars are used in here... you should code "}%" to avoid unnecessary spaces
 % and it is unnecessary to code \cs%
-% got to be carefull with numbers though, cf the texbook...2\relax and 2 % are okey
+% got to be careful with numbers though, cf the texbook...2\relax and 2 % are okey
 
 \def\pgfsys@outerinvoke{\ifpgfpicture\expandafter\pgfsys@invoke\else\expandafter\pgfutil@gobble\fi}
 

tex/generic/pgf/systemlayer/pgfsys.code.tex

@@ -364,7 +364,7 @@
 % Sets the join to a bevel join. See \pgfsys@stroke.
 
 \def\pgfsys@setdash#1#2{\pgf@sys@fail{setting the dashing pattern}}
-% Sets the dashing patter. #1 should be a list of lengths separated by
+% Sets the dashing pattern. #1 should be a list of lengths separated by
 % commas. #2 should be a single dimension.
 %
 % The list of values in #1 is used to determine the lengths of the
@@ -940,15 +940,15 @@
 \def\pgfsys@declarepattern#1#2#3#4#5#6#7#8#9{\pgf@sys@fail{patterns}}
 % This command declares a new colored or uncolored pattern. Uncolored
 % patterns have no inherent color, the color is provided when they are
-% set. Colored patters have an inherent color.
+% set. Colored patterns have an inherent color.
 % #1       = name of the pattern (must be a plain suffix for use in
 %            postscript/pdf/etc.)
 % #2 to #5 = four coordinates describing the corners of a bounding box
 %            of pattern cells
 % #6       = x-step
 % #7       = y-step
 % #8       = pattern code
-% #9       = 0 if uncolored patter, 1 if colored pattern.
+% #9       = 0 if uncolored pattern, 1 if colored pattern.
 
 \def\pgfsys@setpatternuncolored#1#2#3#4{\pgf@sys@fail{patterns}}
 % Sets an uncolored pattern #1 as filling color. The numbers #2, #3,
@@ -1303,7 +1303,7 @@
     \pgfsys@endscope%
     \xdef#1{\the\pgf@sys@id@count}%
     \expandafter\expandafter\expandafter\global\expandafter\pgfsysprotocol@getcurrentprotocol\csname pgf@sys@marker@prot@#1\endcsname%
-    \pgfsys@marker@declare@% curtesy hook
+    \pgfsys@marker@declare@% courtesy hook
     \pgfsysprotocol@setcurrentprotocol\pgfsys@marker@temp%
     \global\advance\pgf@sys@id@count by1\relax%
   }%

tex/generic/pgf/systemlayer/pgfsysanimations.code.tex

@@ -337,7 +337,7 @@
 %
 % Description:
 %
-% Calls \pgfsys@animaion@(no)accumulate and records the setting for
+% Calls \pgfsys@animation@(no)accumulate and records the setting for
 % snapshots.
 
 \def\pgfsysanimkeyaccumulate{\pgfsys@animation@accumulate\pgfsysanim@accumulatetrue}

tex/generic/pgf/utilities/pgfkeyslibraryfiltered.code.tex

@@ -97,7 +97,7 @@
 % ATTENTION: \pgfkeysfiltered can't be nested (yet). Use the
 % \pgfkeyspredicateAND if you need multiple predicates at once.
 % Nesting would produce unexpected results because the current filter
-% state can't be stored/restored without TeX-groups, therefor it is
+% state can't be stored/restored without TeX-groups, therefore it is
 % disabled.
 %
 % ATTENTION: you can't filter error messages.
@@ -479,7 +479,7 @@
     %
     % .is family should
     %  1. '.cd' into the families' path,
-    %  2. define booleans to activate/deactive the family
+    %  2. define booleans to activate/deactivate the family
     %     (see \pgfkeysisfamilyactive)
     %  3. make sure that \pgfkeyshasactivefamily returns true for
     %     the family itself.

tex/generic/pgf/utilities/pgfutil-common.tex

@@ -842,7 +842,7 @@
 \let\pgfutil@write=\write
 \let\pgfutil@read=\read
 
-% curtesy for latex:
+% courtesy for latex:
 \let\pgfutil@protect\relax
 
 % Used by latex for doing reruns