Move advertising

Author: rfc2822

content.mkd

@@ -147,7 +147,7 @@ The `supported-triggers` element(((supported-triggers XML element))) MUST contai
 - `content-update` if the resource supports push notifications on content updates (see {{content-updates}}). It contains a `{DAV:}depth` property that indicates the maximum supported depth.
 - `property-update` if the resource supports push notifications on property updates (see {{property-updates}}). It contains a `{DAV:}depth` property that indicates the maximum supported depth.
 
-Clients can use WebDAV `PROPFIND` to retrieve these properties. WebDAV-Push SHOULD only be advertised to clients which are actually allowed to use it.
+Clients can use WebDAV `PROPFIND` to retrieve these properties.
 
 Example:
 
@@ -449,6 +449,8 @@ WebDAV-Push operates within the usual security context of WebDAV. Servers usuall
 
 It's RECOMMENDED
 
+WebDAV-Push SHOULD only be advertised to clients which are actually allowed to use it.
+
 The general requirements from {{Section 8 of RFC8030}} apply regardless of which transport is used. Especially:
 
 - HTTP over TLS MUST be used for all communications.