update whitelist IP list

Author: harjotgill

Diff for: docs/platforms/github-enterprise-server.md

@@ -8,7 +8,7 @@ sidebar_position: 3
 :::info
 
 This page is for GitHub Enterprise Server (Self-Hosted) users only.  
-If you're using github.com, [log in to CodeRabbit](https://app.coderabbit.ai)
+If you're using `github.com`, [log in to CodeRabbit](https://app.coderabbit.ai)
 and add your repositories from there
 
 :::
@@ -163,7 +163,7 @@ Navigate to the **Advanced** tab in the GitHub App and click on the
 ### **Step 6: Whitelist CodeRabbit IP address**
 
 Use this CodeRabbit IP if your instance requires IP whitelisting
-`35.222.179.152/32`
+`35.222.179.152/32` and `34.170.211.100/32`.
 
 VPN tunneling is available as an add-on package. Please reach out to us at
 [[email protected]](mailto:[email protected]) if you are interested.

Diff for: docs/platforms/self-hosted-gitlab.md

@@ -12,7 +12,10 @@ To initiate the integration, we require specific information. This is essential
 for the initial setup of CodeRabbit within your domain. Once this setup is
 complete, you can log in directly using the OAuth2 flow.
 
-CodeRabbit supports GitLab `16.x` and above. Version `15.x` may experience unexpected issues such as review comments not being posted or the sign up process not working at all. While we won't block the integration, we recommend upgrading your GitLab instance to obtain the intended experience.
+CodeRabbit supports GitLab `16.x` and above. Version `15.x` may experience
+unexpected issues such as review comments not being posted or the sign-up
+process not working at all. While we won't block the integration, we recommend
+upgrading your GitLab instance to obtain the intended experience.
 
 ### **Step 1: Getting Started**
 
@@ -29,7 +32,8 @@ organization and if we find an existing one, we are starting the login process.
 
 ![Untitled](/img/integrations/self-hosted-gitlab-host-url.png)
 
-If the self-managed GitLab instance is not found, we initiate the onboarding process, which can be either manual or automated.
+If the self-managed GitLab instance is not found, we initiate the onboarding
+process, which can be either manual or automated.
 
 ### **Step 3: Onboarding Manual or Automated**
 
@@ -42,31 +46,39 @@ If the self-managed GitLab instance is not found, we initiate the onboarding pro
 Admin access token is required to set up a new CodeRabbit bot user within your
 self-managed instance. The token is needed only once during the initial setup
 process. Once the token is generated, you can set its minimum expiration period.
-This is the standard approach used by other products in this category.
-This is not automatically installing the CodeRabbit
-app across all projects. You will add CodeRabbit manually on the projects you
-wish, as the next step.
+This is the standard approach used by other products in this category. This is
+not automatically installing the CodeRabbit app across all projects. You will
+add CodeRabbit manually on the projects you wish, as the next step.
 
 #### 2. Manual onboarding
 
-For the manual onboarding process we need to create the [CodeRabbit user](#creating-coderabbit-user) and the [OAuth2 GitLab application](#creating-oauth2-application).
+For the manual onboarding process we need to create the
+[CodeRabbit user](#creating-coderabbit-user) and the
+[OAuth2 GitLab application](#creating-oauth2-application).
 ![Untitled](/img/integrations/manual-onboarding.png)
 
 #### **Creating CodeRabbit user**
 
-This feature will work with any user from your organization, but we strongly suggest creating a
-dedicated user called **CodeRabbitAI**. This ensures clarify about which user is used for our
-application and allows for better fine-grained access control.
+This feature will work with any user from your organization, but we strongly
+suggest creating a dedicated user called **CodeRabbitAI**. This ensures clarify
+about which user is used for our application and allows for better fine-grained
+access control.
 
-To create users in GitLab, log in with an instance admin account and follow the steps provided in the [GitLab documentation](https://docs.gitlab.com/ee/user/profile/account/create_accounts.html#create-users-in-admin-area).
-After the user is created, you can retrieve the **User ID** from that user's profile and generate an [**access token**](#generating-personal-access-token).
+To create users in GitLab, log in with an instance admin account and follow the
+steps provided in the
+[GitLab documentation](https://docs.gitlab.com/ee/user/profile/account/create_accounts.html#create-users-in-admin-area).
+After the user is created, you can retrieve the **User ID** from that user's
+profile and generate an [**access token**](#generating-personal-access-token).
 The access token is used to post reviews on merge requests.
 
 #### **Creating OAuth2 application**
 
-For self-managed GitLab, we recommend creating an instance-wide application unless you want the reviews to be limited to a single group or user.
+For self-managed GitLab, we recommend creating an instance-wide application
+unless you want the reviews to be limited to a single group or user.
 
-Please follow the steps outlined in the [GitLab documentation](https://docs.gitlab.com/ee/integration/oauth_provider.html#create-an-instance-wide-application) for creating the application.
+Please follow the steps outlined in the
+[GitLab documentation](https://docs.gitlab.com/ee/integration/oauth_provider.html#create-an-instance-wide-application)
+for creating the application.
 
 Requirements:
 
@@ -79,7 +91,8 @@ GitLab offers an option to generate a personal access token for adding a new
 user and setting up the application in the self-managed instance. To generate
 the token, please follow the process outlined below:
 
-1. Login to your self-hosted instance. For [automated onboarding](#1-automated-onboarding) ensure you have admin rights.
+1. Login to your self-hosted instance. For
+   [automated onboarding](#1-automated-onboarding) ensure you have admin rights.
 2. On the left sidebar, select your avatar.
 3. Select Edit profile.
 4. On the left sidebar, select Access Tokens.
@@ -104,7 +117,7 @@ the token, please follow the process outlined below:
 ### **Step 5: Whitelist CodeRabbit IP address**
 
 Use this CodeRabbit IP if your instance requires IP whitelisting
-`35.222.179.152/32`
+`35.222.179.152/32` and `34.170.211.100/32`.
 
 VPN tunneling is available as an add-on package. Please reach out to us at
 [[email protected]](mailto:[email protected]) if you are interested.