Update text for public aliases docs (#321)

MOD update text for public aliases docs

docs/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

docs/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.10/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.10/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.4/installation/slack/cloud-slack.md

@@ -84,15 +84,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.4/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.5/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.5/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.6/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.6/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.7/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.7/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.8/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.8/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation
 

versioned_docs/version-1.9/installation/slack/cloud-slack.mdx

@@ -76,15 +76,15 @@ After this point, all of your commands will be executed on the default instance.
 
 ### Setting Public Alias for Private Channels
 
-In order to safeguard your confidentiality while enabling seamless integration with Botkube plugins, it's essential to establish a public alias for your private Slack channels. This alias will be accessible solely to Botkube Cloud administrators.
+In order to maintain your confidentiality while using Botkube's plugins, you need to create a public alias for your private Slack channels. This alias will only be visible to Botkube Cloud administrators.
 
 #### During the Botkube Invitation to Private Channels
 
-Upon extending an invitation to Botkube for a private channel, a prompt will appear, guiding you through the process of creating a public alias.
+When you invite Botkube to a private channel, a prompt will appear to guide you through the process of creating a public alias.
 
 #### For Existing Private Channels
 
-Should you need to update an existing alias within a private channel, or if Botkube is already integrated into the channel, you can execute the following command:
+To update an existing alias for a private channel, or if Botkube is already integrated, simply use this command:
 
 ```
 @Botkube cloud set channel-alias <your-public-alias-name>

versioned_docs/version-1.9/operation/common-problems.md

@@ -98,7 +98,7 @@ In order to solve the problem, please refer to the [troubleshooting](../installa
 
 ## I can't see my Slack private channels in Cloud Dashboard
 
-In adherence to Slack privacy policy, private channels are not displayed until a public alias is set for the respective channel. Kindly refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
+To comply with Slack's privacy policy, private channels won't be visible until you create a public alias for the respective channel. Refer to the provided instructions for guidance on completing this process: [Setting Public Alias for Private Channels](../installation/slack/cloud-slack#setting-public-alias-for-private-channels)
 
 ## Air-Gap installation