Update docs/pipeline-components-and-applications/loaders-storage-targ…

…ets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md

Co-authored-by: Nick <[email protected]>

docs/pipeline-components-and-applications/loaders-storage-targets/bigquery-loader/upgrade-guides/2-0-0-upgrade-guide/index.md

@@ -124,9 +124,10 @@ Because `1-0-1` events cannot be loaded into the same column with `1-0-0`, the d
 
 If you create a new schema `1-0-2` that reverts the offending changes and is again compatible with `1-0-0`, the data for events with that schema will be written to the original column as expected.
 
-### Notes
+:::note
 
-- If events with incorrectly evolved schemas do not arrive, then the recovery column would not be created.
-- It is still possible to break loading by overwriting version `1-0-0` of the schema. Please, avoid doing that.
+If events with incorrectly evolved schemas never arrive, then the recovery column would not be created.
+
+:::
 
 You can read more about schema evolution and how recovery columns work [here](/docs/storing-querying/schemas-in-warehouse/index.md?warehouse=bigquery#versioning).