diff --git a/docs/3.0rc/deploy/dynamic-infra/retrieve-workflow-code.mdx b/docs/3.0rc/deploy/dynamic-infra/retrieve-workflow-code.mdx
index e56735a3503d..89ba4e14d7d4 100644
--- a/docs/3.0rc/deploy/dynamic-infra/retrieve-workflow-code.mdx
+++ b/docs/3.0rc/deploy/dynamic-infra/retrieve-workflow-code.mdx
@@ -277,16 +277,3 @@ When using a git repository, Docker image, or cloud-provider storage location, y
 - If you are familiar with git you are likely familiar with the [`.gitignore`](https://git-scm.com/docs/gitignore) file.
 - If you are familiar with Docker you are likely familiar with the [`.dockerignore`](https://docs.docker.com/engine/reference/builder/#dockerignore-file) file.
 - For cloud-provider storage the `.prefectignore` file serves the same purpose and follows a similar syntax as those files. So an entry of `*.pyc` will exclude all `.pyc` files from upload.
-
-## Other code storage creation methods
-
-In earlier versions of Prefect [storage blocks](/3.0rc/develop/connect-third-party/) were the recommended way to store flow code.
-Storage blocks are deprecated.
-
-As shown above, repositories can be referenced directly through interactive prompts with `prefect deploy` or in a `prefect.yaml`.
-When authentication is needed, Secret or Credential blocks can be referenced, and in some cases, created automatically through interactive deployment creation prompts.
-
-## Conclusion
-
-You've seen options for storing your flow code.
-For easier version control, we recommend using Docker-based storage or git-based storage for your production deployments.