Fixed some typos.

doc/assy.rst

@@ -396,7 +396,7 @@ final solution. In an underconstrained system the solver may not move an object
 contribute to the cost function, or if multiple solutions exist (ie. multiple instances
 where the cost function is at a minimum) initial locations can cause the solver to converge on one
 particular solution. For very complicated assemblies setting approximately correct initial locations
-can also reduce the computational time requred.
+can also reduce the computational time required.
 
 
 Constraints
@@ -405,7 +405,7 @@ Constraints
 Constraints are often a better representation of the real world relationship the user wants to
 model than directly supplying locations. In the above example the real world relationship is that
 the bottom face of each cone should touch, which can be modelled with a Plane constraint. When the
-user provides explicit locations (instead of constraints) then they are also reponsible for updating
+user provides explicit locations (instead of constraints) then they are also responsible for updating
 them when, for example, the location of ``cone1`` changes.
 
 When at least one constraint is supplied and the method :meth:`~cadquery.Assembly.solve` is run, an

doc/primer.rst

@@ -369,7 +369,7 @@ where ``a_sketch.arc((1, 2), (2, 3))`` would be dispatched to one method but ``a
 not use keyword arguments to specify positional parameters. For example, you **should not** write
 ``a_sketch.arc(p1=(1, 2), p2=(2, 3), p3=(3, 4))``, instead you should use the previous example.
 Note CadQuery makes an attempt to fall back on the first registered multimethod in the event of a
-dispatch error, but it is still best practise to not use keyword arguments to specify positional
+dispatch error, but it is still best practice to not use keyword arguments to specify positional
 arguments in CadQuery.
 
 An Introspective Example