README.md in gitlab-license-2.4.0 vs README.md in gitlab-license-2.5.0

@@ -25,10 +25,12 @@
 1. Bump the `VERSION` constant in [`lib/gitlab/license/version.rb`](https://dev.gitlab.org/gitlab/gitlab-license/-/blob/master/lib/gitlab/license/version.rb#L3).  This is typically merged as part of the feature MR.
 1. Create a [new release](https://dev.gitlab.org/gitlab/gitlab-license/-/releases) in the project (e.g. `v2.1.0`). For more details on creating a new release, refer to the [documentation](https://dev.gitlab.org/help/user/project/releases/index.md#create-a-release).
 1. [Build the gem](https://guides.rubygems.org/command-reference/#gem-build) to be published: `gem build gitlab-license.gemspec`
 1. [Publish the gem](https://guides.rubygems.org/publishing) to Rubygems: `gem push gitlab-license-2.1.0.gem`
    - Note you will need to be added as an owner in Rubygems in order to publish.
-   - Once this is published, the new version of the gem can be installed in other projects like CustomersDot or GitLab via bundler or using `gem install` directly.
+1. Once published, the new version of the gem can be installed in projects that depend on `gitlab-license` like [CustomersDot](https://gitlab.com/gitlab-org/customers-gitlab-com) and [GitLab](https://gitlab.com/gitlab-org/gitlab).
+   - It is recommended to install the new version in both GitLab and CustomersDot to keep the versions aligned.
+   - This can be installed via bundler or using `gem install` directly.
 
 ## Usage
 
 ```ruby
 # Generate a key pair. You should do this only once.