=back
-This distinction is important because there are some primitves that only apply to paths but not to sequences, and vice versa.
+This distinction is important because there are some primitives that only apply to paths but not to sequences, and vice versa.
Figures are made of ops, path or sequence I<sets> assembled together in a tree.
=back
-You can define automatic coercions from your user point types to L<LaTeX::TikZ::Point> by writing your own L<LaTeX::TikZ::Point::My::User::Point> class.
+You can define automatic coercions from your user point types to L<LaTeX::TikZ::Point> by writing your own C<LaTeX::TikZ::Point::My::User::Point> class.
See L<LaTeX::TikZ::Meta::TypeConstraint::Autocoerce> for the rationale and L<LaTeX::TikZ::Point::Math::Complex> for an example.
=head3 C<< Tikz->line($from => $to) >>
=head3 C<< Tikz->closed_polyline(@points) >>
-Creates a L<LaTeX::TikZ::Set::Polyline> object that cycles through successive eleemnts of C<@points>.
+Creates a L<LaTeX::TikZ::Set::Polyline> object that cycles through successive elemnts of C<@points>.
my $diamond = Tikz->closed_polyline(
Tikz->point(0, 1),
=head3 C<< Tikz->functor(@rules) >>
Creates a L<LaTeX::TikZ::Functor> anonymous subroutine that can be called against L<LaTeX::TikZ::Set> trees to clone them according to the given rules.
-C<@rules> should be made of array references whose first element is the class/role to match against and the second the handler to run.
+C<@rules> should be a list of array references whose first element is the class/role to match against and the second the handler to execute.
# The default is a clone method
my $clone = Tikz->functor;