MINOR - Docs for 1.3 release

openmetadata-docs/content/partials/v1.3/deployment/upgrade/upgrade-prerequisites.md

@@ -156,6 +156,9 @@ removed triggering ES job from Python workflows. Everything happens in the serve
 
 The `openmetadata/ingestion` and `openmetadata/ingestion-base` images now use Python 3.10.
 
+Note that starting release 1.3.0, the `openmetadata-ingestion` package started supporting Python 3.11. We'll
+migrate the images to 3.11 in the next release.
+
 ### Python SDK Auth Mechanisms
 
 We cleaned all the Python SDK code related to any auth system that is not JWT token. Bots deprecated that behavior 2 releases ago
@@ -182,7 +185,7 @@ This is what has been removed:
 
 ### Custom Connectors
 
-In 1.3.0 we started registered more information from Ingestion Pipelines status' in the platform. This required
+In 1.3.0 we started registering more information from Ingestion Pipelines status' in the platform. This required
 us to create new JSON Schemas for the added properties, that before were only used in the Ingestion Framework.
 
 Due to this, we need to update one import and one of its properties' names.
@@ -195,11 +198,10 @@ And we renamed its property `stack_trace` to `stackTrace` to follow the naming c
 
 ### SQL Lineage
 
-With 1.3.0 we have renamed the `sqllineage` package to `collate_sqllineage`, this change has been made to avoid any conflict with open source version of `sqllineage`. In case you are using this package in your python scripts please make sure to rename your imports: 
+In the `collate-sqllineage` dependency, we have renamed the `sqllineage` import to `collate_sqllineage`. 
+
+This change has been made to avoid any conflict with the open source version of `sqllineage`. 
+In case you are using this package directly in your python scripts please make sure to rename your imports: 
 
 - From `from sqllineage.xxx import xxx`
 - To `from collate_sqllineage.xxx import xxx`
-
-### Other Changes
-
-- ...

openmetadata-docs/content/v1.3.x/deployment/upgrade/bare-metal.md

@@ -3,10 +3,6 @@ title: Upgrade on Bare Metal
 slug: /deployment/upgrade/bare-metal
 ---
 
-{% note noteType="Warning" %}
-**Please note that the release 1.3 is still in BETA. Only upgrade your dev and test instances.**
-{% /note %}
-
 # Upgrade on Bare Metal
 
 This guide will help you upgrade an OpenMetadata deployment using release binaries.

openmetadata-docs/content/v1.3.x/deployment/upgrade/docker.md

@@ -3,10 +3,6 @@ title: Upgrade on Docker
 slug: /deployment/upgrade/docker
 ---
 
-{% note noteType="Warning" %}
-**Please note that the release 1.3 is still in BETA. Only upgrade your dev and test instances.**
-{% /note %}
-
 # Upgrade on Docker
 
 To run OpenMetadata with Docker, you can simply download the `docker-compose.yml` file. Optionally, we added some

openmetadata-docs/content/v1.3.x/deployment/upgrade/index.md

@@ -3,10 +3,6 @@ title: Upgrade OpenMetadata
 slug: /deployment/upgrade
 ---
 
-{% note noteType="Warning" %}
-**Please note that the release 1.3 is still in BETA. Only upgrade your dev and test instances.**
-{% /note %}
-
 # Upgrade OpenMetadata
 
 In this guide, you will find all the necessary information to safely upgrade your OpenMetadata instance to 1.3.x.

openmetadata-docs/content/v1.3.x/deployment/upgrade/kubernetes.md

@@ -3,10 +3,6 @@ title: Upgrade on Kubernetes
 slug: /deployment/upgrade/kubernetes
 ---
 
-{% note noteType="Warning" %}
-**Please note that the release 1.3 is still in BETA. Only upgrade your dev and test instances.**
-{% /note %}
-
 # Upgrade on Kubernetes
 
 This guide will help you upgrade your OpenMetadata Kubernetes Application with automated helm hooks.