Make imports more clear (#174)

* Make imports more clear

* May as well make the code lint

Author: Oddant1

book/plugins/how-to-guides/create-register-pipeline.md

@@ -18,6 +18,9 @@ Second, `Pipelines` must have `ctx` as their first parameter, which provides the
 Let's take a look at [`q2_diversity.core_metrics`](https://github.com/qiime2/q2-diversity/blob/3fe491062b8a72939111ff66b2f4aeab8c12b16d/q2_diversity/_core_metrics.py#L14) for an example of a function that we can register as a `Pipeline`:
 
 ```python
+from qiime2.plugin import IContext
+
+
 def core_metrics(ctx: IContext,
                  table: Artifact,
                  sampling_depth: int,

book/plugins/how-to-guides/track-the-value-of-auto-params-in-provenance.md

@@ -34,7 +34,8 @@ my_plugin.methods.register_function(
 What changes is the implementation of the underlying Python function:
 
 ```python
-from qiime2.plugin.type import CaptureHolder
+from qiime2.plugin import CaptureHolder
+
 
 def random_seed_method(random_seed: CaptureHolder[int] = None) -> int:
     # Resolve the seed: if the user passed None, generate a random value and