Revert previous docs update

docs/3.0/get-started/quickstart.mdx

@@ -122,8 +122,6 @@ python my_gh_workflow.py
 
 Prefect automatically tracks the state of the flow run and logs the output, which can be viewed directly in the terminal or in the UI.
 
-There are no changes between the original content and the proposed changes. Therefore, the content remains the same.
-
 ## Create a work pool
 
 Running a flow locally is a good start, but most use cases require a remote execution environment.
@@ -166,10 +164,11 @@ Deploy your flow to Prefect Cloud using a managed work pool.
 1. View your new work pool on the **Work Pools** page of the UI.
   </Tab>
 </Tabs>
-
+  
 <Tip>
 You can also choose from other [work pool types](https://docs.prefect.io/concepts/work-pools/#worker-types).
 </Tip>
+
 ## Deploy and schedule your flow
 
 A [deployment](/3.0/deploy/infrastructure-examples/docker/) is used to determine when, where, and how a flow should run.

docs/3.0/resources/upgrade-agents-to-workers.mdx

@@ -32,9 +32,6 @@ from that pool.
 - Improved visibility into the status of each worker, including when a worker was started 
 and when it last polled.
 - Better handling of race conditions for high availability use cases.
-- New filtering capability with `WorkerFilterStatus` that allows for the inclusion or exclusion 
-of specific worker statuses, simplifying deployment by suppressing unnecessary setup instructions 
-in environments with active workers.
 
 ### Work pools
 
@@ -91,11 +88,6 @@ to enable [dryer deployment definitions](/3.0/deploy/infrastructure-examples/doc
     file or use the [`deploy`](/3.0/deploy/infrastructure-examples/docker) 
     function.
 
-5. **Deployment process improvements:**
-
-    Deployment scripts now check for active workers in a work pool before displaying setup instructions. 
-    This ensures that unnecessary instructions are not shown when active workers are present, 
-    streamlining the deployment process and improving user experience.
 ## What's similar
 
 - You can set storage blocks as the pull action in a `prefect.yaml` file.