latest web site changes
diff --git a/docs/concepts/device-notifications/index.html b/docs/concepts/device-notifications/index.html
index fde1247..480e046 100644
--- a/docs/concepts/device-notifications/index.html
+++ b/docs/concepts/device-notifications/index.html
@@ -21,19 +21,19 @@
<title>Device Notifications :: Eclipse Hono™</title>
- <link href="/hono/docs/css/nucleus.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/fontawesome-all.min.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/hybrid.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/featherlight.min.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/perfect-scrollbar.min.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/auto-complete.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/theme.css?1571275523" rel="stylesheet">
- <link href="/hono/docs/css/hugo-theme.css?1571275523" rel="stylesheet">
+ <link href="/hono/docs/css/nucleus.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/fontawesome-all.min.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/hybrid.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/featherlight.min.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/perfect-scrollbar.min.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/auto-complete.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/theme.css?1571361813" rel="stylesheet">
+ <link href="/hono/docs/css/hugo-theme.css?1571361813" rel="stylesheet">
- <link href="/hono/docs/css/theme-hono.css?1571275523" rel="stylesheet">
+ <link href="/hono/docs/css/theme-hono.css?1571361813" rel="stylesheet">
- <script src="/hono/docs/js/jquery-2.x.min.js?1571275523"></script>
+ <script src="/hono/docs/js/jquery-2.x.min.js?1571361813"></script>
<style type="text/css">
:root #header + #content > #left > #rlblock_left{
@@ -83,14 +83,14 @@
<span data-search-clear=""><i class="fas fa-times"></i></span>
</div>
-<script type="text/javascript" src="/hono/docs/js/lunr.min.js?1571275523"></script>
-<script type="text/javascript" src="/hono/docs/js/auto-complete.js?1571275523"></script>
+<script type="text/javascript" src="/hono/docs/js/lunr.min.js?1571361813"></script>
+<script type="text/javascript" src="/hono/docs/js/auto-complete.js?1571361813"></script>
<script type="text/javascript">
var baseurl = "https:\/\/www.eclipse.org\/hono\/docs\/";
</script>
-<script type="text/javascript" src="/hono/docs/js/search.js?1571275523"></script>
+<script type="text/javascript" src="/hono/docs/js/search.js?1571361813"></script>
</div>
@@ -1201,7 +1201,7 @@
- <option id="stable" value="/hono/docs/concepts/device-notifications/" selected>stable (1.0-M7)</option>
+ <option id="stable" value="/hono/docs/concepts/device-notifications/" selected>stable (1.0)</option>
@@ -1361,17 +1361,15 @@
<h2 id="time-until-disconnect-notification">Time until Disconnect Notification</h2>
-<p><em>Devices</em> and <em>Protocol Adapters</em> can notify an application about the fact that a device is connected and ready to receive one or more commands by means of including a <em>time ‘til disconnect</em> (<em>ttd</em>) property in downstream AMQP 1.0 messages containing data originating from a connected device.</p>
+<p><em>Devices</em> and <em>Protocol Adapters</em> can notify an application about the fact that a device is connected and ready to receive one or more commands by means of including a <em>time ‘til disconnect</em> (<em>ttd</em>) property in telemetry or event messages.</p>
<p>The <em>ttd</em> property value indicates the time that the device will stay connected to the protocol adapter.
-Using this value together with the <em>creation-time</em> of the message, an application can determine whether an attempt to send a command to the device has a reasonable chance of succeeding.</p>
-
-<p>The <em>ttd</em> property can be included in any regular telemetry or event message. However, if a device does not have any telemetry data or event to upload to the adapter, it can also use an <a href="/hono/docs/api/event/#empty-notification">empty notification</a> instead.</p>
+Using this value together with the <em>creation-time</em> of the message, an application can determine whether an attempt to send a command to the device has a reasonable chance of succeeding.
+The <em>ttd</em> property can be included in any regular telemetry or event message. However, if a device does not have any telemetry data or event to upload to the adapter, it can also use an <a href="/hono/docs/api/event/#empty-notification">empty notification</a> instead.</p>
<p>Hono includes utility classes that application developers can use to register a callback to be notified when a device sends a <em>ttd</em> notification.
-See Hono’s example module for details where such a notification callback is used.</p>
-
-<p>Please refer to the <a href="/hono/docs/api/telemetry/">Telemetry API</a> and the <a href="/hono/docs/api/event/">Event API</a> for further details.</p>
+See Hono’s example module for details where such a notification callback is used.
+Please refer to the <a href="/hono/docs/api/telemetry/">Telemetry API</a> and the <a href="/hono/docs/api/event/">Event API</a> for further details.</p>
<p>The following table defines the possible values of the <em>ttd</em> property and their semantics:</p>
@@ -1416,15 +1414,12 @@
<h3 id="source-of-the-ttd-value">Source of the <em>ttd</em> Value</h3>
<p>While it seems to be natural that a device itself indicates when it is ready to receive a command, it may not always be
-possible or desirable to do so.</p>
-
-<p>A device could e.g. be not capable to specify the value for <em>ttd</em> in it’s message, or all devices of a particular setup
-would always use the same value for <em>ttd</em>, so it would not make much sense to provide this value always again.</p>
-
-<p>Additionally different protocols may or may not let a sender set specific values for a message, so a device using a
-specific protocol may not be able to provide a value for the <em>ttd</em> property at all.</p>
-
-<p>For these reasons there are (resp. may be) additional ways of setting the value of <em>ttd</em>:</p>
+possible or desirable to do so.
+A device could e.g. be not capable to specify the value for <em>ttd</em> in it’s message, or all devices of a particular setup
+would always use the same value for <em>ttd</em>, so it would not make much sense to provide this value always again.
+Additionally different protocols may or may not let a sender set specific values for a message, so a device using a
+specific protocol may not be able to provide a value for the <em>ttd</em> property at all.
+For these reasons there are (resp. may be) additional ways of setting the value of <em>ttd</em>:</p>
<ul>
<li>Hono’s Tenant and Device Registration APIs support the inclusion of default values for application-properties in the
@@ -1437,9 +1432,8 @@
<h3 id="hono-s-http-protocol-adapter">Hono’s HTTP protocol adapter</h3>
<p>Hono’s HTTP protocol adapter supports the setting of the <em>ttd</em> value in requests explicitly - please refer to the
-<a href="/hono/docs/user-guide/http-adapter/">HTTP Adapter</a> for details.</p>
-
-<p>Alternatively the default property values for devices from the Device Registry can be used (described above).</p>
+<a href="/hono/docs/user-guide/http-adapter/">HTTP Adapter</a> for details.
+Alternatively the default property values for devices from the Device Registry can be used (described above).</p>
<h3 id="hono-s-mqtt-protocol-adapter">Hono’s MQTT protocol adapter</h3>
@@ -2339,20 +2333,20 @@
<div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
<div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
</div>
- <script src="/hono/docs/js/clipboard.min.js?1571275523"></script>
- <script src="/hono/docs/js/perfect-scrollbar.min.js?1571275523"></script>
- <script src="/hono/docs/js/perfect-scrollbar.jquery.min.js?1571275523"></script>
- <script src="/hono/docs/js/jquery.sticky.js?1571275523"></script>
- <script src="/hono/docs/js/featherlight.min.js?1571275523"></script>
- <script src="/hono/docs/js/html5shiv-printshiv.min.js?1571275523"></script>
- <script src="/hono/docs/js/highlight.pack.js?1571275523"></script>
+ <script src="/hono/docs/js/clipboard.min.js?1571361813"></script>
+ <script src="/hono/docs/js/perfect-scrollbar.min.js?1571361813"></script>
+ <script src="/hono/docs/js/perfect-scrollbar.jquery.min.js?1571361813"></script>
+ <script src="/hono/docs/js/jquery.sticky.js?1571361813"></script>
+ <script src="/hono/docs/js/featherlight.min.js?1571361813"></script>
+ <script src="/hono/docs/js/html5shiv-printshiv.min.js?1571361813"></script>
+ <script src="/hono/docs/js/highlight.pack.js?1571361813"></script>
<script>hljs.initHighlightingOnLoad();</script>
- <script src="/hono/docs/js/modernizr.custom.71422.js?1571275523"></script>
- <script src="/hono/docs/js/learn.js?1571275523"></script>
- <script src="/hono/docs/js/hugo-learn.js?1571275523"></script>
+ <script src="/hono/docs/js/modernizr.custom.71422.js?1571361813"></script>
+ <script src="/hono/docs/js/learn.js?1571361813"></script>
+ <script src="/hono/docs/js/hugo-learn.js?1571361813"></script>
- <link href="/hono/docs/mermaid/mermaid.css?1571275523" type="text/css" rel="stylesheet" />
- <script src="/hono/docs/mermaid/mermaid.js?1571275523"></script>
+ <link href="/hono/docs/mermaid/mermaid.css?1571361813" type="text/css" rel="stylesheet" />
+ <script src="/hono/docs/mermaid/mermaid.js?1571361813"></script>
<script>
mermaid.initialize({ startOnLoad: true });
</script>
