Conductor: further explain setup steps

Author: glaubinix

docs/conductor/getting-started.md

@@ -1,25 +1,32 @@
 # Getting started with Conductor
 ##
 
-Conductor will group and schedule automated dependency updates on your own Continuous Integration platform. If the update succeeds, Conductor sends you a pull request to your code hosting platform (GitHub, GitLab, Bitbucket) with the changed composer.lock file and, if necessary, other files modified by Composer plugins or scripts.
+Conductor will group and schedule automated dependency updates on your own Continuous Integration platform. If the update succeeds, Conductor will send you a pull request to your code hosting platform (GitHub, GitLab, Bitbucket) with the changed composer.lock file and, if necessary, other files modified by Composer plugins or scripts.
 
 To use Conductor:
 
-- You need to be approved for early access to Conductor. [Join to the waitlist](/features/conductor) and wait for approval.
+- You need to be approved for early access to Conductor. [Join the waitlist](/features/conductor) and wait for approval.
 - You need a Private Packagist trial or subscription on the cloud plan.
-- You need to add a workflow to your Continuous Integration platform to run Composer updates, described below.
+- You need to add a synchronization with your code hosting platform.
+- You need to add a workflow to your Continuous Integration platform to run Composer updates.
 
-## Add packages to update automatically
+## Add a synchronization
 
-Once you have a Private Packagist organization and Conductor is enabled for you, log into your Private Packagist organization and click on the "Updates" tab in the main navigation.  
+Once you have a Private Packagist organization and Conductor is enabled for you, log into your Private Packagist organization and head to the "Settings" tab in the main navigation.
+Under the "Synchronization" entry you can add [one or more synchronizations](/features/integration-github-bitbucket-gitlab.md) with an organization on your code hosting platform.
+This is how you grant us access to your repositories. Once done we will automatically add any repository with a composer.json file in the root directory as a package to Private Packagist.
 
+## Configure Conductor for your packages
+
+Access the "Conductor" tab in the main navigation to see a list of available packages that can be managed via Conductor.
+Each package shown is linked to a repository where you would like to receive pull requests from Conductor. This usually includes all your Composer projects.
 Conductor will manage dependencies for packages added to Private Packagist [via synchronization](/features/integration-github-bitbucket-gitlab.md) that have a composer.lock file committed to the repository.
 
-## Create a workflow on your CI
+To get started, click on the configure link displayed for the package where you want to use Conductor and follow the instructions for your Continuous Integration platform.
 
 ### GitHub Actions
 
-Create a new GitHub Actions workflow in `.github/workflows/dependency-update.yaml` of your GitHub repository using the template below:
+Create a new GitHub Actions workflow in `.github/workflows/conductor.yaml` of your GitHub repository using the template below:
 
 CONDUCTOR_GITHUB_ACTIONS_WORKFLOW
 
@@ -31,13 +38,13 @@ We recommend to create a dedicated authentication token with update access. You
 
 ![Create Authentication Token](/Resources/public/img/docs/conductor/authentication-token.png)
 
-The contents of the variable should look like 
+The contents of the variable should look like
 
 ```json
 {"http-basic": {"repo.packagist.com": {"username": "token", "password": "packagist_out_73a81c..." }}}
 ```
 
-Conductor needs to verify your CI setup before you can start receiving pull requests.
+Conductor needs to verify your CI setup before you can start receiving PRs.
 
 ## Verify your CI setup
 
@@ -58,7 +65,7 @@ When you run into errors, troubleshoot and fix them. You can trigger the workflo
 
 ## How scheduling works
 
-- Navigate to the "Updates" tab in your Private Packagist organization 
+- Navigate to the "Conductor" tab in your Private Packagist organization
 - Click on the name of your package
 
 The list shows groups of all available updates to be scheduled. Each group of updates is called a task. Conductor will schedule only one task at a time. All others are waiting for the task on top of the list to be successful or paused.  
@@ -79,7 +86,7 @@ If all these steps succeeded, Private Packagist creates a pull request for the n
 ![Conductor Pull Request](https://packagist.com/img/features/auto-updates/merged-PR-for-a-security-updated.png)
 
 Once you reviewed the changes and merged the PR, Conductor will schedule the next task.      
-If you close the PR, the task will be paused and Conductor will schedule the next task. This is the same effect as using the "Pause" button in the UI. Conductor won't attempt to update the dependency to this exact version again but will schedule updates with newer versions.  
+If you close the PR, the task will be paused and Conductor will schedule the next task. This is the same effect as using the "Pause" button in the UI. Conductor won't attempt to update the dependency to this exact version again but will schedule updates with newer versions.
 
 If you want to schedule any other task in the list, click on its name and use the button "Schedule now to create a PR".