Update migration guide

docs/migration-guides/1.15-1.17.md

@@ -1,16 +1,16 @@
 # Migrate from 1.15 to 1.17
 
 To upgrade Kyma from 1.15 to 1.17 you have to perform two steps:
-1. upgrade to a Release Candidate version of Kyma tagged 1.16.0-rc3,
+1. upgrade to a Release Candidate version of Kyma tagged 1.16.0-rc4,
 2. upgrade to an official Release 1.17 version of Kyma
 
  This document contains two sections describing actions you have to perform before or after each step.
 
-## Migrate from 1.15 to 1.16.0-rc3
+## Migrate from 1.15 to 1.16.0-rc4
 
 ### Istio
 
-Kyma 1.16.0-rc3 comes with a new Istio version: 1.5.10, which introduces a new custom resource for Istio installation. If you use any overrides provided by Helm or IstioControlPlane, migrate them to the new [IstioOperator](https://istio.io/v1.5/docs/reference/config/istio.operator.v1alpha1/). See [an example of IstioOperator](https://kyma-project.io/docs/1.16/components/service-mesh/#configuration-istio-custom-configuration) for more information.
+Kyma 1.16.0-rc4 comes with a new Istio version: 1.5.10, which introduces a new custom resource for Istio installation. If you use any overrides provided by Helm or IstioControlPlane, migrate them to the new [IstioOperator](https://istio.io/v1.5/docs/reference/config/istio.operator.v1alpha1/). See [an example of IstioOperator](https://kyma-project.io/docs/1.16/components/service-mesh/#configuration-istio-custom-configuration) for more information.
 
 All Istio-related objects in Kyma are updated, but the migration may be necessary for the Istio objects created manually in your cluster.
 Please read the [Istio upgrade notes](https://istio.io/latest/news/releases/1.5.x/announcing-1.5/upgrade-notes/) for the details.
@@ -20,7 +20,7 @@ In addition, consider migrating existing Authentication Policy to equivalent Pee
 
 ### Eventing
 
-In Release Candidate 1.16.0-rc3, we remove the support for Knative-Serving from Kyma. After the upgrade Knative-Serving is still installed and fully functional in the cluster, but can be removed easily in order to free resources. Removing Knative-Serving will not affect supported Kyma functionality.
+In Release Candidate 1.16.0-rc4, we remove the support for Knative-Serving from Kyma. After the upgrade Knative-Serving is still installed and fully functional in the cluster, but can be removed easily in order to free resources. Removing Knative-Serving will not affect supported Kyma functionality.
 
 Before you remove Knative-Serving from the cluster, make sure that you create a backup of any of your own resources that used Knative-Serving. You can do this by running:
 
@@ -54,25 +54,25 @@ kubectl delete crd \
 
 ### Logging
 
-In Release Candidate 1.16.0-rc3, we change the `instance` label on the logs corresponding to the Pod name to `pod`, which fits the observability ecosystem better.
+In Release Candidate 1.16.0-rc4, we change the `instance` label on the logs corresponding to the Pod name to `pod`, which fits the observability ecosystem better.
 Also, the `container` label for a function pointing to `lambda` in the previous releases now points to `function`.
 If you search for the logs from a function with the `container: lambda` filter, you will need to change it to `container: function` from this release on.
 
 ### Kyma with Compass
 
 > **CAUTION:** This step only applies to Kyma **with Compass**.
 
-In Kyma 1.17, the name of [this Application Connector Secret](https://github.com/kyma-project/kyma/blob/release-1.17/resources/core/charts/gateway/templates/application-connector-certs.yaml) changed from `kyma-gateway-certs-cacert` to `app-connector-certs`. This resulted in the CA certificate data (`cacert`) being lost at upgrade from 1.16.0-rc3 to 1.17. To prevent that, we introduced a [migration job](https://github.com/kyma-project/kyma/blob/release-1.17/resources/core/charts/gateway/templates/cacert-migrate-job.yaml) that makes sure the data copied from the old Kyma version to the new one persists and is migrated correctly.
+In Kyma 1.17, the name of [this Application Connector Secret](https://github.com/kyma-project/kyma/blob/release-1.17/resources/core/charts/gateway/templates/application-connector-certs.yaml) changed from `kyma-gateway-certs-cacert` to `app-connector-certs`. This resulted in the CA certificate data (`cacert`) being lost at upgrade from 1.16.0-rc4 to 1.17. To prevent that, we introduced a [migration job](https://github.com/kyma-project/kyma/blob/release-1.17/resources/core/charts/gateway/templates/cacert-migrate-job.yaml) that makes sure the data copied from the old Kyma version to the new one persists and is migrated correctly.
 
-To make sure this job runs correctly, run this command **after** you've performed an upgrade to Release Candidate 1.16.0-rc3 and **before** upgrade to 1.17:
+To make sure this job runs correctly, run this command **after** you've performed an upgrade to Release Candidate 1.16.0-rc4 and **before** upgrade to 1.17:
 
 ```bash
 kubectl patch compassconnection compass-connection --type=merge -p '{"spec":{"refreshCredentialsNow":true}}'
 ```
 
 This ensures that the client gets reloaded and the correct `cacert` data is saved in Kyma 1.17.
 
-## Migrate from 1.16.0-rc3 to 1.17
+## Migrate from 1.16.0-rc4 to 1.17
 
 ### Istio