diff --git a/.bumpversion.cfg b/.bumpversion.cfg
index 1bf426ce36c..f5a86d075b5 100644
--- a/.bumpversion.cfg
+++ b/.bumpversion.cfg
@@ -3,9 +3,11 @@ current_version = 0.17.0-alpha
 commit = True
 tag = False
 parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\-[a-z]+)?
-serialize = 
+serialize =
 	{major}.{minor}.{patch}-alpha
 
 [bumpversion:file:.bumpversion.cfg]
 
 [bumpversion:file:.env]
+
+[bumpversion:file:docs/tutorials/upgrading-airbyte.md]
diff --git a/docs/tutorials/building-a-python-source.md b/docs/tutorials/building-a-python-source.md
index a975a03cbe0..2d7a8f11fcd 100644
--- a/docs/tutorials/building-a-python-source.md
+++ b/docs/tutorials/building-a-python-source.md
@@ -196,6 +196,8 @@ The template fills in most of the information for the readme for you. Unless the
 
 Open the following file: `airbyte-config/init/src/main/resources/seed/source_definitions.yaml`. You'll find a list of all the connectors that Airbyte displays in the UI. Pattern match to add your own connector. Make sure to generate a new _unique_ UUIDv4 for the `sourceDefinitionId` field. You can get one [here](https://www.uuidgenerator.net/). After you do, run `./gradlew :airbyte-config:init:build` \(this command generates some necessary configuration files\).
 
+Note that for simple and quick testing use cases, you can also do this step [using the UI](../integrations/custom-connectors.md#adding-your-connectors-in-the-ui).
+
 #### Step 12: Add docs
 
 Each connector has its own documentation page. By convention, that page should have the following path: in `docs/integrations/sources/<source-name>.md`. For the documentation to get packaged with the docs, make sure to add a link to it in `docs/SUMMARY.md`. You can pattern match doing that from existing connectors.
diff --git a/docs/tutorials/connecting-el-with-t-using-sql.md b/docs/tutorials/connecting-el-with-t-using-sql.md
index 2dcf0288af6..c282d49ac29 100644
--- a/docs/tutorials/connecting-el-with-t-using-sql.md
+++ b/docs/tutorials/connecting-el-with-t-using-sql.md
@@ -83,14 +83,14 @@ Therefore, it is possible to extract these SQL files, modify them and run it you
 You would be able to find these at the following location inside the server's docker container:
 
 ```text
-/tmp/workspace/${NORMALIZE_WORKSPACE}/build/run/airbyte_utils/models/generated/<your_table_name>.sql
+/tmp/workspace/${NORMALIZE_WORKSPACE}/build/run/airbyte_utils/models/generated/airbyte_tables/<schema>/<your_table_name>.sql
 ```
 
 In order to extract them, you can run:
 
 ```bash
 docker cp airbyte-server:/tmp/workspace/${NORMALIZE_WORKSPACE}/build/run/airbyte_utils/models/generated/* models/
-ls models
+find models
 ```
 
 Example Output:
diff --git a/docs/tutorials/upgrading-airbyte.md b/docs/tutorials/upgrading-airbyte.md
index c77fd421522..ca472d56a8e 100644
--- a/docs/tutorials/upgrading-airbyte.md
+++ b/docs/tutorials/upgrading-airbyte.md
@@ -10,6 +10,7 @@ All minor and major version releases requiring updating the data that Airbyte st
 
 {% hint style="info" %}
 If you inadvertently upgrade to a version of Airbyte that is not compatible with your data, the docker containers will not start up and will log an error stating the incompatibility. In these cases, you should downgrade to the previous version that worked and follow the steps below.
+On the other hand, if you don't mind losing your current Airbyte configuration or have never setup any proper connections yet, you can skip the migrating operations and jump directly to step 5 below.
 {% endhint %}
 
 ## Upgrading \(Docker\)
@@ -39,10 +40,10 @@ If you inadvertently upgrade to a version of Airbyte that is not compatible with
 Here's an example of what might look like with the values filled in. It assumes that the downloaded `airbyte_archive.tar.gz` is in `/tmp`.
 
 ```bash
-docker run --rm -v /tmp:/config airbyte/migration:0.15.0-alpha --\
+docker run --rm -v /tmp:/config airbyte/migration:0.17.0-alpha --\
   --input /config/airbyte_archive.tar.gz\
   --output /config/airbyte_archive_migrated.tar.gz\
-  --target-version 0.15.0-alpha
+  --target-version 0.17.0-alpha
 ```
 
 {% hint style="info" %}