diff --git a/docs/cicd/deployment-pipelines/intro-to-deployment-pipelines.md b/docs/cicd/deployment-pipelines/intro-to-deployment-pipelines.md
index ca1250cfb4..16a3818083 100644
--- a/docs/cicd/deployment-pipelines/intro-to-deployment-pipelines.md
+++ b/docs/cicd/deployment-pipelines/intro-to-deployment-pipelines.md
@@ -165,9 +165,9 @@ The deployment process lets you clone content from one stage in the deployment p
 
 Folders enable users to efficiently organize and manage workspace items in a familiar way. When you deploy content that contains folders to a different stage, the folder hierarchy of the applied items is automatically applied.
 
-With the current view of the folders hierarchy, you can select for deployment, only items in the same folder level. You cannot select items across folders.
+With the current view of the folders hierarchy, you can select for deployment only items in the same folder level. You cannot select items across folders.
  
-Flat list view of deployment pipelines allows you to select items regardless of its location. With the flat list view, you can select items across folders, regarding their location in the workspace. For more information, see [flat list view](deploy-content.md#flat-list-view).
+The flat list view of deployment pipelines allows you to select items regardless of its location. With the flat list view, you can select items across folders, regardless of their location in the workspace. For more information, see [flat list view](deploy-content.md#flat-list-view).
 
 To deploy content to another stage, at least one item must be selected. When you deploy content from one stage to another, the items being copied from the source stage overwrite the paired item in the stage you're in according to the [pairing rules](./assign-pipeline.md#item-pairing). Items that don't exist in the source stage remain as is.