diff --git a/docs/Property_Metadata_Binding_f5aa4bb.md b/docs/Property_Metadata_Binding_f5aa4bb.md
index 7872cb63..46c7973c 100644
--- a/docs/Property_Metadata_Binding_f5aa4bb.md
+++ b/docs/Property_Metadata_Binding_f5aa4bb.md
@@ -35,6 +35,15 @@ The binding must then know the metadata part of the binding expression. The path
     var myLabel = new sap.m.Label({text:"{/#Company/CompanyName/@sap:label}"});
     ```
 
+    To use the absolute binding for a property that doesn't occur in an EntityType of the default model, the reference to the correct model defined in the manifest can be added as a prefix. If you’re not adding the model, the framework will tell you in the development console that the mentioned Entity is not present. Defining the target model can be done by adding `myModel>` in the beginning of the binding string.
+
+    Example:
+
+    ```js
+    
+    var myLabel = new sap.m.Label({text:"{myModel>/#Company/CompanyName/@sap:label}"});
+    ```
+
 -   Relative Binding
 
     A relative binding path can be resolved relative to a data path/context.
diff --git a/docs/css/BusinessSuiteInAppSymbols.woff b/docs/css/BusinessSuiteInAppSymbols.woff
index 5a1bb492..03f89ea0 100644
Binary files a/docs/css/BusinessSuiteInAppSymbols.woff and b/docs/css/BusinessSuiteInAppSymbols.woff differ