Correct tutorial bullet points wrongly edited by Gitbook. (#2275)

- List correct link to tutorial page.
- Correct bad Gitbook changes.

reviewer: Chris

airbyte-commons/src/main/java/io/airbyte/commons/version/AirbyteVersion.java

@@ -111,7 +111,7 @@ public static void assertIsCompatible(final String version1, final String versio
     if (isCompatible(version1, version2)) {
       throw new IllegalStateException(String.format(
           "Version mismatch between %s and %s.\n" +
-              "Please Upgrade or Reset your Airbyte Database, see more at https://docs.airbyte.io/tutorials/tutorials/upgrading-airbyte",
+              "Please upgrade or reset your Airbyte Database, see more at https://docs.airbyte.io/tutorials/upgrading-airbyte",
           cleanVersion1, cleanVersion2));
     }
   }

airbyte-server/src/main/java/io/airbyte/server/handlers/ArchiveHandler.java

@@ -147,7 +147,7 @@ private void checkImport(Path tempFolder) throws IOException, JsonValidationExce
     LOGGER.info(String.format("Checking Airbyte Version to import %s", importVersion));
     if (AirbyteVersion.isCompatible(version, importVersion)) {
       throw new IOException(String.format("Imported VERSION (%s) is incompatible with current Airbyte version (%s).\n" +
-          "Please Upgrade your Airbyte Archive, see more at https://docs.airbyte.io/tutorials/tutorials/upgrading-airbyte\n",
+          "Please upgrade your Airbyte Archive, see more at https://docs.airbyte.io/tutorials/upgrading-airbyte\n",
           importVersion, version));
     }
     databaseArchiver.checkVersion(version);

docs/tutorials/upgrading-airbyte.md

@@ -49,31 +49,31 @@ docker run --rm -v /tmp:/config airbyte/migration:0.15.0-alpha --\
 It may seem confusing that you need to specify the target version twice. The version passed as `--target-version` specifies the version to which the data will be migrated. Specifying the target version in the docker container tag makes sure that you are pulling an image that at least has the migration for the version you want. Technically the version used in the docker tag can be equal to or greater than the version you are upgrading to. For the simplicity of this tutorial we have them match.
 {% endhint %}
 
-1. Turn off Airbyte fully.
+5. Turn off Airbyte fully.
 
    ```text
    docker-compose down
    ```
 
-2. Delete the existing Airbyte docker volumes. _Note: Make sure you have already exported your data \(step 3\). This command is going to delete your data in Docker!_
+6. Delete the existing Airbyte docker volumes. _Note: Make sure you have already exported your data \(step 3\). This command is going to delete your data in Docker!_
 
    ```bash
    docker volume rm $(docker volume ls -q | grep airbyte)
    ```
 
-3. Upgrade the docker instance to new version.
+7. Upgrade the docker instance to new version.
 
    i. If you are running Airbyte from a cloned version of the Airbyte repo and want to use the current most recent stable version, just `git pull`.
 
    ii. If you are running Airbyte from a `.env`, edit the `VERSION` field in that file to be the desired version.
 
-4. Bring Airbyte back online.
+8. Bring Airbyte back online.
 
    ```text
    docker-compose up
    ```
 
-5. Complete Preferences section. In the subsequent setup page click "Skip Onboarding". Navigate to the Admin page in the UI. Then go to the Configuration Tab. Click Import. This will prompt you to upload the migrated archive to Airbyte. After this completes, your upgraded Airbyte instance will now be running with all of your original configuration.
+9. Complete Preferences section. In the subsequent setup page click "Skip Onboarding". Navigate to the Admin page in the UI. Then go to the Configuration Tab. Click Import. This will prompt you to upload the migrated archive to Airbyte. After this completes, your upgraded Airbyte instance will now be running with all of your original configuration.
 
 This step will throw an exception if the data you are trying to upload does not match the version of Airbyte that is running.