Merge pull request mendix#6457 from joostverhoog/license

External entities do not require a separate license anymore

Author: MarkvanMents

content/en/docs/developerportal/deploy/general/licensing-apps-outside-mxcloud.md

@@ -25,7 +25,6 @@ Unlicensed apps, running outside the Mendix Cloud, have a number of restrictions
 | **Number of Concurrent Users** | 6 | Depends on your pricing plan.¹ ² |
 | **Time limitation** | Runtime stops after 2-4 hours (randomly chosen) regardless of user activity.³ | Does not have a time limitation. |
 | **Number of Named Users** | No Limit | Depends on your pricing plan.¹ |
-| **Data Hub** | 1000 objects per day | Depends on your pricing plan.¹ |
 
 ¹ More information on the capabilities of different license options is available on [Mendix Platform Pricing](http://www.mendix.com/pricing).
 

content/en/docs/refguide/modeling/domain-model/external-entities.md

@@ -15,10 +15,6 @@ External entities can be used with local entities. However, as the datasets are
 
 To follow how to add external entities from the [Integration Pane](/refguide/integration-pane/), see [Adding External Entities](#adding-external-entities).
 
-{{% alert color="info" %}}
-A license is required to use Mendix Data Hub and connect to external data sources through consumed OData services in your apps.
-{{% /alert %}}
-
 ## 2 Adding an External Entity to an App {#adding-external-entities}
 
 To add an external entity to your app model, follow these steps:

content/en/docs/refguide/modeling/integration/odata-services/wrap-services-odata.md

@@ -34,8 +34,8 @@ OData is a set of best practices for building REST APIs that standardizes many a
 
 ### 2.2 Compatibility with Data Hub
 
-Wrapping a service, API, or database in OData ensures compatibility with the [Catalog](/catalog/). Published OData services are registered automatically in the [Catalog](/catalog/), making them easily usable in other Mendix apps. Discovering and using OData resources in [external entities](/refguide/external-entities/) is made easy for licensed users on a [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/), as [published OData Services](/refguide/published-odata-services/) are registered automatically in the [Catalog](/catalog/) and made available in the Studio Pro [Integration Pane](/refguide/integration-pane/).
-
+Wrapping a service, API, or database in OData ensures compatibility with the [Catalog](/catalog/). Published OData services are registered automatically in the [Catalog](/catalog/), making them easily usable in other Mendix apps. Discovering and using OData resources in [external entities](/refguide/external-entities/) is made easy if you are using [Mendix Cloud](/developerportal/deploy/mendix-cloud-deploy/), as [published OData Services](/refguide/published-odata-services/) are registered automatically in the [Catalog](/catalog/) and made available in the Studio Pro [Integration Pane](/refguide/integration-pane/).
+  
 ## 3 Non-Persistable Entities as Published OData Resources {#npe-published-odata}
 
 When building a connector or integration, you might only need to move data from back-end services to the client apps instead of storing the data in the database. To support this, you can expose [non-persistable entities](/refguide/entities/#non-persistable-entity) as [published OData resources](/refguide/published-odata-resource/). Previously, only persistable entities could be exposed as published OData resources.