Merge pull request #1058 from GandalfDG/doc_ref_fixes

Fix broken references in documentation

Author: jmwright

doc/assy.rst

@@ -451,8 +451,8 @@ When creating a Point constraint, the ``param`` argument can be used to specify
 between the two centers. This offset does not have a direction associated with it, if you want to
 specify an offset in a specific direction then you should use a dummy :class:`~cadquery.Vertex`.
 
-The Point constraint uses the :meth:`~cadquery.occ_impl.Shape.Center` to find the center of the
-argument. Hence it will work with all subclasses of :class:`~caquery.occ_impl.Shape`.
+The Point constraint uses the :meth:`~cadquery.Shape.Center` to find the center of the
+argument. Hence it will work with all subclasses of :class:`~cadquery.Shape`.
 
 .. cadquery::
 

doc/examples.rst

@@ -1,5 +1,7 @@
 .. _examples:
 
+.. currentmodule:: cadquery
+
 *********************************
 CadQuery Examples
 *********************************

doc/primer.rst

@@ -166,7 +166,7 @@ For example, this::
 Will actually create 4 circles, because ``vertices()`` selects 4 vertices of a rectangular face, and the ``circle()`` method
 iterates on each member of the stack.
 
-This is really useful to remember  when you author your own plugins. :py:meth:`cadquery.cq.Workplane.each` is useful for this purpose.
+This is really useful to remember  when you author your own plugins. :py:meth:`cadquery.Workplane.each` is useful for this purpose.
 
 CadQuery API layers
 ---------------------------
@@ -284,6 +284,8 @@ Below is presented the different ways you can interact with the different API la
 Fluent API <=> Direct API
 -------------------------
 
+.. currentmodule:: cadquery
+
 Here are all the possibilities you have to get an object from the Direct API (i.e a topological object).
 
 You can end the Fluent API call chain and get the last object on the stack with :py:meth:`Workplane.val` alternatively you can get all