Remove old text

Author: jesp209i

umbraco-cloud/set-up/project-settings/umbraco-cicd/KnownLimitationsAndConsiderations.md

@@ -29,11 +29,9 @@ Attaching a CI/CD pipeline to a flexible environment is currently not possible.
 * **Direct Commits to Umbraco Git Repos**: Any commits made directly to the Umbraco-git-repos will cause the process to fail.
 * **Remote Build/Test Options**: It is currently not possible to skip the first build step before committing.
 * **Incomplete API**:
-  * The list endpoint lacks filtering capabilities.
   * The promotion endpoint for transitioning from dev to stage to live is not fully functional yet.
 * **Hotfix Deployments**: Direct deployments to a specific environment are not supported at this time.
 * **Lack of Predefined Tasks**: There are no Umbraco-provided Azure DevOps tasks or GitHub Actions available.
 * **No Webhooks**: Currently, there's no webhook support for real-time feedback to the pipeline; polling is the only option.
 * **Casing Conflicts**: Be cautious of casing issues, such as having a README.md file created by Azure DevOps and a `Readme.md` file from the default Umbraco Cloud, as this can cause conflicts in the cloud Git repository.
-* **Documentation Alignment**: We are in the process of updating our documentation to align with standard Umbraco guidelines.
-* **Developer Experience**: Plans are underway to create Umbraco-specific Azure DevOps tasks and GitHub Actions to enhance the developer experience.
+