Removed 'please note' phrase

See: https://docs.gitlab.com/ee/development/documentation/styleguide/word_list.html\#please

doc/administration/geo/disaster_recovery/background_verification.md

@@ -198,7 +198,7 @@ nodes, and comparing the output between them.
 
 In GitLab EE 12.1, Geo calculates checksums for attachments, LFS objects, and
 archived traces on secondary nodes after the transfer, compares it with the
-stored checksums, and rejects transfers if mismatched. Please note that Geo
+stored checksums, and rejects transfers if mismatched. Geo
 currently does not support an automatic way to verify these data if they have
 been synced before GitLab EE 12.1.
 

doc/administration/geo/replication/configuration.md

@@ -286,9 +286,9 @@ The two most obvious issues that can become apparent in the dashboard are:
    - You are using a custom certificate or custom CA (see the [troubleshooting document](troubleshooting.md)).
    - The instance is firewalled (check your firewall rules).
 
-Please note that disabling a **secondary** node stops the synchronization process.
+Disabling a **secondary** node stops the synchronization process.
 
-Please note that if `git_data_dirs` is customized on the **primary** node for multiple
+If `git_data_dirs` is customized on the **primary** node for multiple
 repository shards you must duplicate the same configuration on each **secondary** node.
 
 Point your users to the [Using a Geo Site guide](usage.md).

doc/administration/postgresql/replication_and_failover.md

@@ -497,7 +497,7 @@ Here is a list and description of each machine and the assigned IP:
 
 All passwords are set to `toomanysecrets`, please do not use this password or derived hashes and the `external_url` for GitLab is `http://gitlab.example.com`.
 
-Please note that after the initial configuration, if a failover occurs, the PostgresSQL master will change to one of the available secondaries until it is failed back.
+After the initial configuration, if a failover occurs, the PostgresSQL master will change to one of the available secondaries until it is failed back.
 
 #### Example recommended setup for Consul servers
 
@@ -628,7 +628,7 @@ All passwords are set to `toomanysecrets`, please do not use this password or de
 
 The `external_url` for GitLab is `http://gitlab.example.com`
 
-Please note that after the initial configuration, if a failover occurs, the PostgresSQL master will change to one of the available secondaries until it is failed back.
+After the initial configuration, if a failover occurs, the PostgresSQL master will change to one of the available secondaries until it is failed back.
 
 #### Example minimal configuration for database servers
 

doc/administration/redis/replication_and_failover.md

@@ -106,7 +106,7 @@ is not initiated.
 As an example, if you have `6` Redis nodes, a maximum of `3` can be
 simultaneously down.
 
-Please note that there are different requirements for Sentinel nodes.
+There are different requirements for Sentinel nodes.
 If you host them in the same Redis machines, you may need to take
 that restrictions into consideration when calculating the amount of
 nodes to be provisioned. See [Sentinel setup overview](#sentinel-setup-overview)
@@ -539,7 +539,7 @@ Here is a list and description of each **machine** and the assigned **IP**:
 - `10.0.0.3`: Redis Replica 2 + Sentinel 3
 - `10.0.0.4`: GitLab application
 
-Please note that after the initial configuration, if a failover is initiated
+After the initial configuration, if a failover is initiated
 by the Sentinel nodes, the Redis nodes are reconfigured and the **Primary**
 changes permanently (including in `redis.conf`) from one node to the other,
 until a new failover is initiated again.

doc/administration/redis/replication_and_failover_external.md

@@ -260,7 +260,7 @@ Here is a list and description of each **machine** and the assigned **IP**:
 - `10.0.0.3`: Redis Replica 2 + Sentinel 3
 - `10.0.0.4`: GitLab application
 
-Please note that after the initial configuration, if a failover is initiated
+After the initial configuration, if a failover is initiated
 by the Sentinel nodes, the Redis nodes are reconfigured and the **Primary**
 changes permanently (including in `redis.conf`) from one node to the other,
 until a new failover is initiated again.

doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md

@@ -16,7 +16,7 @@ and your [support options](https://about.gitlab.com/support/), before attempting
 this information.
 
 WARNING:
-Please note that some of these scripts could be damaging if not run correctly,
+Some of these scripts could be damaging if not run correctly,
 or under the right conditions. We highly recommend running them under the
 guidance of a Support Engineer, or running them in a test environment with a
 backup of the instance ready to be restored, just in case.

doc/api/users.md

@@ -1757,7 +1757,7 @@ Example response:
 ]
 ```
 
-Please note that `last_activity_at` is deprecated, please use `last_activity_on`.
+`last_activity_at` is deprecated. Use `last_activity_on` instead.
 
 ## User memberships (admin only)
 

doc/ci/triggers/index.md

@@ -205,7 +205,7 @@ file. The parameter is of the form:
 variables[key]=value
 ```
 
-This information is also exposed in the UI. Please note that _values_ are only viewable by Owners and Maintainers.
+This information is also exposed in the UI. _Values_ are only viewable by users with the Owner and Maintainer role.
 
 ![Job variables in UI](img/trigger_variables.png)
 

doc/development/audit_event_guide/index.md

@@ -83,7 +83,7 @@ def audit_remove(model)
 end
 ```
 
-Please note that this method does not support actions that are asynchronous, or
+This method does not support actions that are asynchronous, or
 span across multiple processes (for example, background jobs).
 
 ### Using standard method call to record single event

doc/development/cicd/index.md

@@ -159,7 +159,7 @@ On top of that, we have the following types of jobs:
 - `Ci::Bridge` ... The job to trigger a downstream pipeline.
 - `GenericCommitStatus` ... The job to be executed in an external CI/CD system e.g. Jenkins.
 
-Please note that, when you use the "Job" terminology in codebase, readers would
+When you use the "Job" terminology in codebase, readers would
 assume that the class/object is any type of above.
 If you specifically refer `Ci::Build` class, you should not name the object/class
 as "job" as this could cause some confusions. In documentation,

doc/development/code_review.md

@@ -125,7 +125,7 @@ with [domain expertise](#domain-experts).
 1. If your merge request includes an addition of, or changes to a [Feature spec](testing_guide/testing_levels.md#frontend-feature-tests), it must be **approved by a [Quality maintainer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_qa) or [Quality reviewer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_qa)**.
 1. If your merge request introduces a new service to GitLab (Puma, Sidekiq, Gitaly are examples), it must be **approved by a [product manager](https://about.gitlab.com/company/team/)**. See the [process for adding a service component to GitLab](adding_service_component.md) for details.
 
-- (*1*): Please note that specs other than JavaScript specs are considered backend code.
+- (*1*): Specs other than JavaScript specs are considered backend code.
 - (*2*): We encourage you to seek guidance from a database maintainer if your merge
   request is potentially introducing expensive queries. It is most efficient to comment
   on the line of code in question with the SQL queries so they can give their advice.

doc/development/contributing/merge_request_workflow.md

@@ -12,7 +12,7 @@ to GitLab code, tests, and documentation. The issues that are specifically suita
 for community contributions are listed with the [`Accepting merge requests`](issue_workflow.md#label-for-community-contributors)
 label, but you are free to contribute to any issue you want.
 
-Please note that if an issue is marked for the current milestone at any time, even
+If an issue is marked for the current milestone at any time, even
 when you are working on it, a GitLab Inc. team member may take over the merge request
 in order to ensure the work is finished before the release date.
 

doc/development/database/constraint_naming_convention.md

@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 The most common option is to let Rails pick the name for database constraints and indexes or let PostgreSQL use the defaults (when applicable). However, when needing to define custom names in Rails or working in Go applications where no ORM is used, it is important to follow strict naming conventions to improve consistency and discoverability.
 
 The table below describes the naming conventions for custom PostgreSQL constraints.
-Please note that the intent is not to retroactively change names in existing databases but rather ensure consistency of future changes.
+The intent is not to retroactively change names in existing databases but rather ensure consistency of future changes.
 
 | Type                     | Syntax                                                                                            | Notes                                                                                                                                                                       | Examples                                                                                                          |
 |--------------------------|---------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|

doc/development/distributed_tracing.md

@@ -101,7 +101,7 @@ trace in a hierarchical time-line.
 ## Using Jaeger without the GitLab Developer Kit
 
 Distributed Tracing can be enabled in non-GDK development environments as well as production or
-staging environments, for troubleshooting. Please note that at this time, this functionality is
+staging environments, for troubleshooting. At this time, this functionality is
 experimental, and not supported in production environments at present. In this first release, it is intended to be
 used for debugging in development environments only.
 

doc/development/emails.md

@@ -26,7 +26,7 @@ mailer.unknown_sign_in_email(user, ip, time).deliver_later
 To view rendered emails "sent" in your development instance, visit
 [`/rails/letter_opener`](http://localhost:3000/rails/letter_opener).
 
-Please note that [S/MIME signed](../administration/smime_signing_email.md) emails
+[S/MIME signed](../administration/smime_signing_email.md) emails
 [cannot be currently previewed](https://github.com/fgrehm/letter_opener_web/issues/96) with
 `letter_opener`.
 
@@ -125,7 +125,7 @@ Examples of valid email keys:
 - `1234567890abcdef1234567890abcdef-unsubscribe` (unsubscribe from a conversation)
 - `1234567890abcdef1234567890abcdef` (reply to a conversation)
 
-Please note that the action `-issue-` is used in GitLab as the handler for the Service Desk feature.
+The action `-issue-` is used in GitLab as the handler for the Service Desk feature.
 
 ### Legacy format
 
@@ -137,7 +137,7 @@ These are the only valid legacy formats for an email handler:
 - `namespace`
 - `namespace+action`
 
-Please note that `path/to/project` is used in GitLab as the handler for the Service Desk feature.
+In GitLab, the handler for the Service Desk feature is `path/to/project`.
 
 ---
 

doc/development/fe_guide/design_anti_patterns.md

@@ -12,7 +12,8 @@ generally be avoided.
 Throughout the GitLab codebase, there may be historic uses of these anti-patterns. Please [use discretion](https://about.gitlab.com/handbook/engineering/#balance-refactoring-and-velocity)
 when figuring out whether or not to refactor, when touching code that uses one of these legacy patterns.
 
-**Please note:** For new features, anti-patterns are not necessarily prohibited, but it is **strongly suggested** to find another approach.
+NOTE:
+For new features, anti-patterns are not necessarily prohibited, but it is **strongly suggested** to find another approach.
 
 ## Shared Global Object (Anti-pattern)
 

doc/development/fe_guide/design_patterns.md

@@ -9,7 +9,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 The following design patterns are suggested approaches for solving common problems. Use discretion when evaluating
 if a certain pattern makes sense in your situation. Just because it is a pattern, doesn't mean it is a good one for your problem.
 
-**Please note:** When adding a design pattern to this document, be sure to clearly state the **problem it solves**.
+NOTE:
+When adding a design pattern to this document, be sure to clearly state the **problem it solves**.
 
 ## TBD
 

doc/development/fe_guide/graphql.md

@@ -110,7 +110,7 @@ Default client accepts two parameters: `resolvers` and `config`.
 
 If you are make multiple queries to the same Apollo client object you might encounter the following error: "Store error: the application attempted to write an object with no provided ID but the store already contains an ID of SomeEntity". [This error only should occur when you have made a query with an ID field for a portion, then made another that returns what would be the same object, but is missing the ID field.](https://github.com/apollographql/apollo-client/issues/2510#issue-271829009)
 
-Please note this is being tracked in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/326101) and the documentation will be updated when this issue is resolved.
+This is being tracked in [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/326101) and the documentation will be updated when this issue is resolved.
 
 ## GraphQL Queries
 

doc/development/fe_guide/troubleshooting.md

@@ -38,7 +38,7 @@ See [this video](https://youtu.be/-BkEhghP-kM) for an in-depth overview and inve
 + expect(wrapper.findComponent(ChildComponent).props()).toMatchObject(...);
 ```
 
-Please note that `toMatchObject` actually changes the nature of the assertion and won't fail if some items are **missing** from the expectation.
+`toMatchObject` actually changes the nature of the assertion and won't fail if some items are **missing** from the expectation.
 
 ### Script issues
 

doc/development/testing_guide/end_to_end/index.md

@@ -91,7 +91,7 @@ subgraph "`gitlab-org/gitlab-qa-mirror` pipeline"
 1. The result of the [`gitlab-org/gitlab-qa-mirror` pipeline](https://gitlab.com/gitlab-org/gitlab-qa-mirror) is being
    propagated upstream (through polling from upstream pipelines), through [`gitlab-org/build/omnibus-gitlab-mirror`](https://gitlab.com/gitlab-org/build/omnibus-gitlab-mirror), back to the [`gitlab-org/gitlab`](https://gitlab.com/gitlab-org/gitlab) merge request.
 
-Please note, we plan to [add more specific information](https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/156)
+We plan to [add more specific information](https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/156)
 about the tests included in each job/scenario that runs in `gitlab-org/gitlab-qa-mirror`.
 
 NOTE:

doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md

@@ -432,7 +432,7 @@ To run the LDAP tests on your local with TLS enabled, follow these steps:
 
    `127.0.0.1    gitlab.test`
 
-   You can then run tests against GitLab in a Docker container on `https://gitlab.test`. Please note that the TLS certificate [checked into the GitLab-QA repository](https://gitlab.com/gitlab-org/gitlab-qa/-/tree/9ffb9ad3be847a9054967d792d6772a74220fb42/tls_certificates/gitlab) is configured for this domain.
+   You can then run tests against GitLab in a Docker container on `https://gitlab.test`. The TLS certificate [checked into the GitLab-QA repository](https://gitlab.com/gitlab-org/gitlab-qa/-/tree/9ffb9ad3be847a9054967d792d6772a74220fb42/tls_certificates/gitlab) is configured for this domain.
 1. Run the OpenLDAP container with TLS enabled. Change the path to [`gitlab-qa/fixtures/ldap`](https://gitlab.com/gitlab-org/gitlab-qa/-/tree/9ffb9ad3be847a9054967d792d6772a74220fb42/fixtures/ldap) directory to your local checkout path:
 
    ```shell

doc/integration/elasticsearch.md

@@ -238,7 +238,7 @@ The following Elasticsearch settings are available:
 | `Password`                                                 | The password of your Elasticsearch instance. |
 | `Number of Elasticsearch shards`                      | Elasticsearch indexes are split into multiple shards for performance reasons. In general, you should use at least 5 shards, and indexes with tens of millions of documents need to have more shards ([see below](#guidance-on-choosing-optimal-cluster-configuration)). Changes to this value do not take effect until the index is recreated. You can read more about tradeoffs in the [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/scalability.html). |
 | `Number of Elasticsearch replicas`                    | Each Elasticsearch shard can have a number of replicas. These are a complete copy of the shard, and can provide increased query performance or resilience against hardware failure. Increasing this value will greatly increase total disk space required by the index. |
-| `Limit namespaces and projects that can be indexed`   | Enabling this will allow you to select namespaces and projects to index. All other namespaces and projects will use database search instead. Please note that if you enable this option but do not select any namespaces or projects, none will be indexed. [Read more below](#limiting-namespaces-and-projects).
+| `Limit namespaces and projects that can be indexed`   | Enabling this will allow you to select namespaces and projects to index. All other namespaces and projects will use database search instead. If you enable this option but do not select any namespaces or projects, none will be indexed. [Read more below](#limiting-namespaces-and-projects).
 | `Using AWS hosted Elasticsearch with IAM credentials` | Sign your Elasticsearch requests using [AWS IAM authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html), [AWS EC2 Instance Profile Credentials](https://docs.aws.amazon.com/codedeploy/latest/userguide/getting-started-create-iam-instance-profile.html#getting-started-create-iam-instance-profile-cli), or [AWS ECS Tasks Credentials](https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-iam-roles.html). Please refer to [Identity and Access Management in Amazon Elasticsearch Service](https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-ac.html) for details of AWS hosted Elasticsearch domain access policy configuration. |
 | `AWS Region`                                          | The AWS region in which your Elasticsearch service is located. |
 | `AWS Access Key`                                      | The AWS access key. |
@@ -567,7 +567,7 @@ For basic guidance on choosing a cluster configuration you may refer to [Elastic
 
 ### Advanced Search integration settings guidance
 
-- The `Number of Elasticsearch shards` setting usually corresponds with the number of CPUs available in your cluster. For example, if you have a 3-node cluster with 4 cores each, this means you will benefit from having at least 3*4=12 shards in the cluster. Please note, it's only possible to change the shards number by using [Split index API](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-split-index.html) or by reindexing to a different index with a changed number of shards.
+- The `Number of Elasticsearch shards` setting usually corresponds with the number of CPUs available in your cluster. For example, if you have a 3-node cluster with 4 cores each, this means you will benefit from having at least 3*4=12 shards in the cluster. It's only possible to change the shards number by using [Split index API](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-split-index.html) or by reindexing to a different index with a changed number of shards.
 - The `Number of Elasticsearch replicas` setting should most of the time be equal to `1` (each shard will have 1 replica). Using `0` is not recommended, because losing one node will corrupt the index.
 
 ### Indexing large instances

doc/integration/saml.md

@@ -707,7 +707,7 @@ Examples:
 - [Auth0](https://auth0.com/docs/protocols/saml-protocol/configure-auth0-as-saml-identity-provider)
 - [PingOne by Ping Identity](https://docs.pingidentity.com/bundle/pingone/page/xsh1564020480660-1.html)
 
-Please note that GitLab provides the following setup notes for guidance only.
+GitLab provides the following setup notes for guidance only.
 If you have any questions on configuring the SAML app, please contact your provider's support.
 
 ### Okta setup notes

doc/user/admin_area/moderate_users.md

@@ -144,7 +144,7 @@ A user can be deactivated from the Admin Area. To do this:
 1. Select the **{settings}** **User administration** dropdown.
 1. Select **Deactivate**.
 
-Please note that for the deactivation option to be visible to an admin, the user:
+For the deactivation option to be visible to an admin, the user:
 
 - Must be currently active.
 - Must not have signed in, or have any activity, in the last 90 days.

doc/user/application_security/index.md

@@ -114,7 +114,7 @@ rules:
 
 If you add the security scanning jobs as described in [Security scanning with Auto DevOps](#security-scanning-with-auto-devops) or [Security scanning without Auto DevOps](#security-scanning-without-auto-devops) to your `.gitlab-ci.yml` each added [security scanning tool](#security-scanning-tools) behave as described below.
 
-For each compatible analyzer, a job is created in the `test`, `dast` or `fuzz` stage of your pipeline and runs on the next new branch pipeline. Features such as the [Security Dashboard](security_dashboard/index.md), [Vulnerability Report](vulnerability_report/index.md), and [Dependency List](dependency_list/index.md) that rely on this scan data only show results from pipelines on the default branch. Please note that one tool may use many analyzers.
+For each compatible analyzer, a job is created in the `test`, `dast` or `fuzz` stage of your pipeline and runs on the next new branch pipeline. Features such as the [Security Dashboard](security_dashboard/index.md), [Vulnerability Report](vulnerability_report/index.md), and [Dependency List](dependency_list/index.md) that rely on this scan data only show results from pipelines on the default branch. One tool might use many analyzers.
 
 Our language and package manager specific jobs attempt to assess which analyzer(s) they should run for your project so that you can do less configuration.
 

doc/user/application_security/offline_deployments/index.md

@@ -61,7 +61,7 @@ mirroring the packages inside your own offline network.
 Once a vulnerability is found, you can interact with it. Read more on how to
 [address the vulnerabilities](../vulnerabilities/index.md).
 
-Please note that in some cases the reported vulnerabilities provide metadata that can contain
+In some cases the reported vulnerabilities provide metadata that can contain
 external links exposed in the UI. These links might not be accessible within an offline environment.
 
 ### Resolving vulnerabilities

doc/user/group/saml_sso/index.md

@@ -91,7 +91,7 @@ After you set up your identity provider to work with GitLab, you must configure
 ![Group SAML Settings for GitLab.com](img/group_saml_settings_v13_12.png)
 
 NOTE:
-Please note that the certificate [fingerprint algorithm](../../../integration/saml.md#notes-on-configuring-your-identity-provider) must be in SHA1. When configuring the identity provider, use a secure signature algorithm.
+The certificate [fingerprint algorithm](../../../integration/saml.md#notes-on-configuring-your-identity-provider) must be in SHA1. When configuring the identity provider, use a secure signature algorithm.
 
 ### SSO enforcement
 
@@ -128,15 +128,15 @@ When [configuring your identity provider](#configuring-your-identity-provider),
 For providers not listed below, you can refer to the [instance SAML notes on configuring an identity provider](../../../integration/saml.md#notes-on-configuring-your-identity-provider)
 for additional guidance on information your identity provider may require.
 
-Please note that GitLab provides the following for guidance only.
+GitLab provides the following information for guidance only.
 If you have any questions on configuring the SAML app, please contact your provider's support.
 
 ### Azure setup notes
 
-Please follow the Azure documentation on [configuring single sign-on to applications](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/view-applications-portal) with the notes below for consideration.
+Follow the Azure documentation on [configuring single sign-on to applications](https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/view-applications-portal) with the notes below for consideration.
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
-For a demo of the Azure SAML setup including SCIM, see [SCIM Provisioning on Azure Using SAML SSO for Groups Demo](https://youtu.be/24-ZxmTeEBU). Please note that the video is outdated in regard to
+For a demo of the Azure SAML setup including SCIM, see [SCIM Provisioning on Azure Using SAML SSO for Groups Demo](https://youtu.be/24-ZxmTeEBU). The video is outdated in regard to
 objectID mapping and the [SCIM documentation should be followed](scim_setup.md#azure-configuration-steps).
 
 | GitLab Setting | Azure Field |

doc/user/group/settings/import_export.md

@@ -138,4 +138,4 @@ To help avoid abuse, by default, users are rate limited to:
 | Download export  | 1 download per group per minute  |
 | Import           | 6 groups per minute                |
 
-Please note that GitLab.com may have [different settings](../../gitlab_com/index.md#importexport) from the defaults.
+GitLab.com may have [different settings](../../gitlab_com/index.md#importexport) from the defaults.

doc/user/project/highlighting.md

@@ -44,7 +44,7 @@ To disable highlighting entirely, use `gitlab-language=text`. Lots more fun shen
 /other-file gitlab-language=text?token=Error
 ```
 
-Please note that these configurations only take effect when the `.gitattributes`
+These configurations only take effect when the `.gitattributes`
 file is in your [default branch](repository/branches/default.md).
 
 NOTE:

doc/user/project/integrations/bamboo.md

@@ -55,7 +55,7 @@ service in GitLab.
 1. If necessary, enter username and password for a Bamboo user that has
    access to trigger the build plan. Leave these fields blank if you do not require
    authentication.
-1. Save or optionally click **Test Settings**. Please note that **Test Settings**
+1. Save or optionally click **Test Settings**. **Test Settings**
    actually triggers a build in Bamboo.
 
 ## Troubleshooting

doc/user/project/settings/import_export.md

@@ -209,4 +209,4 @@ To help avoid abuse, by default, users are rate limited to:
 | Download export  | 1 download per group per minute  |
 | Import           | 6 projects per minute                |
 
-Please note that GitLab.com may have [different settings](../../gitlab_com/index.md#importexport) from the defaults.
+GitLab.com may have [different settings](../../gitlab_com/index.md#importexport) from the defaults.

doc/user/project/web_ide/index.md

@@ -454,7 +454,7 @@ when:
 
 The Web IDE has a few limitations:
 
-- Interactive Terminals is in a beta phase and continues to be improved in upcoming releases. In the meantime, please note that the user is limited to having only one
+- Interactive Terminals is in a beta phase and continues to be improved in upcoming releases. In the meantime, the user is limited to having only one
   active terminal at a time.
 
 - LFS files can be rendered and displayed but they cannot be updated and committed using the Web IDE. If an LFS file is modified and pushed to the repository, the LFS pointer in the repository is overwritten with the modified LFS file content.