chore: Add Canny items

docs/administration.landing-zones.md

@@ -23,12 +23,12 @@ Platform Operators can configure a custom Landing Zone [meshTag](./meshstack.met
 
 ## Include Building Blocks as part of the Landing Zone
 
-For all types of platforms it is possible to include Building Blocks as part of the Landing Zone. These Building Blocks can be configured to be either:
+For all types of platforms it is possible to include building blocks as part of the landing zone. These building blocks can be configured to be either:
 
-- Required: this means the Building Block has to be booked by the Workspace user. This is useful when you want to enforce
-  the usage of a particular Building Block in combination with the Landing Zone.
-- Optional: this means the Building Block can be optionally added by the Workspace user, but they are not required to
-  do so and they could decide not to add it
+- Required: this means the building block has to be booked by the workspace user. This is useful when you want to enforce
+  the usage of a particular building block in combination with the landing zone.
+- Optional: this means the building block can be optionally added by the workspace user, but they are not required to
+  do so and they could decide not to add it.
 
 ## Defining Quotas
 

docs/marketplace.service-instances.md

@@ -42,6 +42,7 @@ Via the `pen` icon you can edit the service instance. Changing the name is alway
 
 > ⚠️ This feature is deprecated and will be removed in a future release.
 > Please use [Building Blocks](./administration.building-blocks.md) with Platform Tenant Identifiers as inputs instead!
+> For more information, have a look at the [deprecation item](https://meshcloud.canny.io/deprecations/p/deprecation-of-osb-tenant-bindings)
 
 Some services require to bind a meshTenant. In that case you have to select one of your meshTenants when creating a binding.
 
@@ -53,6 +54,7 @@ It is not possible to select the same meshTenant for multiple bindings of the sa
 
 > ⚠️ This feature is deprecated and will be removed in a future release.
 > Please use [Building Blocks](./administration.building-blocks.md) for Workspaces instead!
+> For more information, have a look at the [deprecation item](https://meshcloud.canny.io/deprecations/p/deprecation-of-osb-service-instance-sharing)
 
 If the Service Broker [supports](meshstack.meshmarketplace.profile.md#sharable-service-instances) it, service Instances can be shared between meshProjects of the same meshWorkspace. It is only sharable to projects, if the meshLocation the Service Instance relates to exists in the meshProject the instance shall be shared with. This is currently only supported for the global OSB Services.
 

docs/meshstack.meshmarketplace.profile.md

@@ -66,6 +66,7 @@ Also see [Metrics-based Metering](meshstack.meshmarketplace.metrics-metering.md#
 
 > ⚠️ This feature is deprecated and will be removed in a future release.
 > Please use [Building Blocks](./administration.building-blocks.md) with sensitive inputs instead!
+> For more information, please see the [deprecation item](https://meshcloud.canny.io/deprecations/p/deprecation-of-osb-sensitive-services).
 
 Usually the OSB Services platform shows credentials of a Service Binding to the users, who have access to it. If the Service Broker requires a more secure handling of credentials, it can provide the `sensitive` metadata for the according service in the OSB catalog.
 
@@ -87,6 +88,7 @@ The OSB Services platform does not store any credentials provided by bindings on
 
 > ⚠️ This feature is deprecated and will be removed in a future release.
 > Please use [Building Blocks](./administration.building-blocks.md) with Platform Tenant Identifiers as inputs instead!
+> For more information, have a look at the [deprecation item](https://meshcloud.canny.io/deprecations/p/deprecation-of-osb-tenant-bindings)
 
 A Service Broker can define its services to be tenant-aware by providing a `tenantAware` flag in service metadata of the service definition. Tenant-aware Services can receive special Service Bindings that provide the meshTenant context to the Service Broker using a special [Bind Resource Object](https://github.com/openservicebrokerapi/servicebroker/blob/v2.15/spec.md#bind-resource-object). When users create a tenant service binding in the OSB Services platform, they have to select a meshTenant. Only the meshTenants of the meshProject, which contains the Service Instance, can be selected.
 
@@ -110,6 +112,8 @@ Please review the [Tenant Services documentation](./meshstack.meshmarketplace.te
 
 > ⚠️ This feature is deprecated and will be removed in a future release.
 > Please use [Building Blocks](./administration.building-blocks.md) for Workspaces instead!
+> For more information, have a look at the [deprecation item](https://meshcloud.canny.io/deprecations/p/deprecation-of-osb-service-instance-sharing)
+
 
 [Service Instance Sharing](marketplace.service-instances.md#share-service-instance) must be activated by Service Broker via `shareable` flag on metadata of the service definition.