all suggestions from code review

Author: pscheit

docs/conductor/getting-started.md

@@ -5,33 +5,28 @@ Conductor will group and schedule automated Dependency Updates on your own Conti
 
 To use Conductor:
 
-- You need to be approved for early access to conductor. [Join to the waitlist](http://packagist.com.lo/features/conductor) and wait for approval.
-- You need a Private Packagist trial or subscription (Cloud or Self-Hosted).
+- You need to be approved for early access to Conductor. [Join to 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.
 
-## First steps
+## Add packages to update automatically
 
-Once you have a Private Packagist Subscription and Conductor is enabled for your subscription, log into your Private Packagist organization and click on the "Updates" tab in the main navigation.  
-Conductor will list packages:
- - added to Private Packagist via synchronization
- - having a composer.lock file commited to the repository
- - having the Private Packagist repository added to the composer.json
+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.  
 
-If you do not see your package, follow the instructions on your organization page to add the custom repository to the composer.json of your package.  
+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.
 
-Most convenient way to set up Conductor is to configure your CI in the Private Packagist UI. The manual steps are outlined below:
+If you do not see your package, follow the instructions on your organization page to add the custom repository to the composer.json of your package.  
 
 ## Create a workflow on your CI
 
 ### GitHub Actions
 
-Create a new GitHub Actions workflow in `.github/workflows/dependency-update.yaml` of your package repository using the template below:
+Create a new GitHub Actions workflow in `.github/workflows/dependency-update.yaml` of your GitHub repository using the template below:
 
 CONDUCTOR_GITHUB_ACTIONS_WORKFLOW
 
 1. Adjust the PHP Version used in the "Install PHP" step
 2. Commit and push the workflow to your main branch of your package repository
-3. Review the steps to commit and push to your repository
 
 Create a secret `COMPOSER_AUTH` with the Composer authentication configuration [as described here](https://getcomposer.org/doc/articles/authentication-for-private-packages.md#authentication-using-the-composer-auth-environment-variable) to access Private Packagist.  
 We recommend to create a dedicated authentication token with update access. You can copy and paste the contents for the secret from the Private Packagist UI while creating the token in "Settings" -> "Authentication Tokens". Remove the single quotes around the value.
@@ -44,11 +39,11 @@ The contents of the variable should look like
 {"http-basic": {"repo.packagist.com": {"username": "token", "password": "packagist_out_73a81c..." }}}
 ```
 
-Conductor needs to verify your setup before you can [start receiving Pull Requests](#how-scheduling-works). 
+Conductor needs to [verify your CI setup](#verify-your-ci-setup) before you can start receiving pull requests.
 
 ## How scheduling works
 
-- Go to your package on the updates tab in your Private Packagist organization 
+- Navigate to the "Updates" 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.  
@@ -69,11 +64,11 @@ If all these steps succeeded, Private Packagist creates a pull request for the j
 ![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, 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 of the list by clicking on its name and using the button "Schedule now to create a PR".  
+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".
 
-Tasks fixing security issues have a higher priority. They will be moved to the top of the list and scheduled right away.  
+Tasks fixing security issues have a higher priority. They will be moved to the top of the list and scheduled right away even if there already is a PR for another task open.
 
 ## Verify your CI setup
 
@@ -85,9 +80,9 @@ The verification task will only execute `composer update nothing` and will not r
 - Click on the task "Verify the continuous integration setup"
 - Use the "Schedule now" button to test your setup
 
-You can see the state of your task and last events for the task. Once the task is executed, watch your CI platform: 
+You can see the state of your task and the last events for the task. Once the task is executed, watch your CI platform:
 You should see a run for the just added workflow. Examine the run if it succeeded.
 
 If it was successful your CI configuration is verified and complete. Conductor will trigger your workflow with the next task in the list. This time it will send a pull request. 
 
-When you ran into errors, troubleshoot and fix. You can trigger the workflow again by restarting the CI verification task. The restart button is available after the first execution.  
+When you run into errors, troubleshoot and fix them. You can trigger the workflow again by restarting the CI verification task. The restart button is available after the first execution.