MultiVCS: update a few screenshots and text

Author: peterdeme

docs/assets/screenshots/Screenshot from 2021-06-11 14-52-40.png

@@ -4,7 +4,7 @@ Spacelift supports using Azure DevOps as the source of code for your [stacks](..
 
 ## Setting up the integration
 
-In order to set up the integration from the Spacelift side, please navigate to the VCS management page, click on the **Set up integration** button in the top right corner and choose Azure DevOps.
+In order to set up the integration from the Spacelift side, please navigate to the **Source code** page, click on the **Set up integration** button in the top right corner and choose Azure DevOps.
 
 This form will appear:
 
@@ -72,7 +72,7 @@ If all the data is correct, click **Set up** in the bottom right corner.
 
 ### Configuring Webhooks
 
-In order for Spacelift to be notified of any changes made in your repositories, you need to setup webhooks in Azure DevOps. You can find your **webhook endpoint** and **webhook secret** after clicking the 3 dots next to the integration name on the VCS providers page, and then clicking **See details**.
+In order for Spacelift to be notified of any changes made in your repositories, you need to setup webhooks in Azure DevOps. You can find your **webhook endpoint** and **webhook secret** after clicking the 3 dots next to the integration name on the **Source code** page, and then clicking **See details**.
 
 !!! note
     Space-level integrations will be listed to users with **read** access to the integration Space. Integration details however contain sensitive information (such as webhook secret) so they are only visible to those with **admin** access. On the other hand, default integrations are visible to all users of the account, but only **root** Space admins can see the details of them.
@@ -119,7 +119,7 @@ When creating a Stack, you will now be able to choose the Azure DevOps provider
 
 ## Deleting the Integration
 
-If you no longer need the integration, you can delete it by clicking the 3 dots next to the integration name on the VCS providers page, and then clicking **Delete**. You need **admin** access to the integration Space to be able to delete it.
+If you no longer need the integration, you can delete it by clicking the 3 dots next to the integration name on the **Source code page**, and then clicking **Delete**. You need **admin** access to the integration Space to be able to delete it.
 
 <p align="center">
   <img src="../../assets/screenshots/azure_devops_deletion_button.png"/>

docs/assets/screenshots/azure_devops_details.png

@@ -4,7 +4,7 @@
 
 ## Setting up the integration
 
-In order to set up the integration from the Spacelift side, please navigate to the VCS management page, click on the **Set up integration** button in the top right corner and choose Bitbucket Cloud.
+In order to set up the integration from the Spacelift side, please navigate to the **Source code** page, click on the **Set up integration** button in the top right corner and choose Bitbucket Cloud.
 
 This form will appear:
 
@@ -43,7 +43,7 @@ After doing all this you should have all fields filled in.
   <img src="../../assets/screenshots/Screenshot from 2021-06-11 10-50-38.png" width="450" alt="Filled in Bitbucket Cloud integration form" />
 </p>
 
-Once you've finished saving the form, you can find your **webhook endpoint** after clicking the 3 dots next to the integration name on the VCS providers page, and then clicking **See details**.
+Once you've finished saving the form, you can find your **webhook endpoint** after clicking the 3 dots next to the integration name on the **Source code** page, and then clicking **See details**.
 
 <p align="center">
   <img src="../../assets/screenshots/Screenshot from 2021-06-11 14-52-40.png" width="450" alt="Integration details" />
@@ -73,14 +73,14 @@ When creating a Stack, you will now be able to choose the Bitbucket Cloud provid
 
 ## Deleting the Integration
 
-If you no longer need the integration, you can delete it by clicking the 3 dots next to the integration name on the VCS providers page, and then clicking **Delete**. You need **admin** access to the integration Space to be able to delete it.
+If you no longer need the integration, you can delete it by clicking the 3 dots next to the integration name on the **Source code** page, and then clicking **Delete**. You need **admin** access to the integration Space to be able to delete it.
 
 <p align="center">
   <img src="../../assets/screenshots/azure_devops_deletion_button.png"/>
 </p>
 
 !!! warning
-    Please note that you can delete integrations while stacks are still using them. See the next section for more details.
+    Please note that you can delete source code integrations while stacks are still using them. See the next section for more details.
 
 ### Consequences
 

docs/integrations/source-control/azure-devops.md

@@ -43,7 +43,7 @@ In some cases, using the Spacelift application from the Marketplace is not an op
 
 #### Creating the custom application
 
-In order to do so, navigate to the **VCS management** page, click on the **Set up integration** button and choose GitHub.
+In order to do so, navigate to the **Source code** page, click on the **Set up integration** button and choose GitHub.
 You will be presented with two options:
 
 ![](<../../assets/screenshots/CleanShot 2022-09-16 at 09.38.30.png>)
@@ -156,7 +156,7 @@ Now that you've created a GitHub App and configured it in Spacelift, the last st
 
 ### Via Spacelift UI
 
-On the VCS management page:
+On the Source code page:
 
 <p align="center">
   <img src="../../assets/screenshots/github_install_app.png" width="400"/>
@@ -396,7 +396,7 @@ By default Spacelift uses the GitHub API to download a tarball containing the so
 
     ![](<../../assets/screenshots/CleanShot 2022-09-16 at 10.24.08.png>)
 
-    You can now remove the integration via the *Delete* button on the *VCS management* page:
+    You can now remove the integration via the *Delete* button on the *Source code* page:
 
     <p align="center"><img src="../../assets/screenshots/Gitlab_delete.png"/></p>