Merge pull request #1547 from PrefectHQ/doc_tweak

Remove pitfall doc reference to DockerEnvironment

docs/core/concepts/common-pitfalls.md

@@ -42,7 +42,7 @@ is_serializable(my_flow) # returns True / False
 Note that this is _not_ a guarantee, but merely a helper to catch issues early on.
 
 ::: tip
-A good rule of thumb is that every object / function you rely on should either be explicitly attached to some attribute of the flow (e.g., a task) or importable via some library that is included in your `DockerEnvironment` requirements.
+A good rule of thumb is that every object / function you rely on should either be explicitly attached to some attribute of the flow (e.g., a task) or importable via some library that is included in your `Docker` storage requirements.
 :::
 
-A more robust (albeit longer) process to check that your Flow makes it through the serialization and deployment is to build its `DockerEnvironment` locally and check that the Flow can be deserialized within the container.  For details on how to do this, see the corresponding section in the [local debugging](../tutorials/local-debugging.html#locally-check-your-flow-s-environment) tutorial.
+A more robust (albeit longer) process to check that your Flow makes it through the serialization and deployment is to build its `Docker` storage locally and check that the Flow can be deserialized within the container.  For details on how to do this, see the corresponding section in the [local debugging](../tutorials/local-debugging.html#locally-check-your-flow-s-docker-storage) tutorial.