Update pipelines.md (#31022)

Removing an optional step 5 that mentions a now deprecated feature that we are ultimately replacing with Granular Access Controls.

Author: makenzie-dd

content/en/logs/log_configuration/pipelines.md

@@ -185,9 +185,8 @@ By default, Datadog tracers can [automatically inject span IDs into your logs][1
     **Note**: The pipeline filtering is applied before any of the pipeline's processors. For this reason, you cannot filter on an attribute that is extracted in the pipeline itself.
 
 4. Name your pipeline.
-5. (Optional) Grant editing access to processors in the pipeline. If you assign a role to a pipeline, the role receives `logs_write_processor` [permissions][12] specifically scoped to that pipeline. Roles with `logs_write_processor` permissions assigned globally (by editing role), cannot be selected, as they have access to all pipelines.
-6. (Optional) Add a description and tags to the pipeline to indicate its purpose and ownership. Pipeline tags do not affect logs, but can be used to filter and search within the [Pipelines page][5].
-7. Press **Create**.
+5. (Optional) Add a description and tags to the pipeline to indicate its purpose and ownership. Pipeline tags do not affect logs, but can be used to filter and search within the [Pipelines page][5].
+6. Press **Create**.
 
 An example of a log transformed by a pipeline: