Fix invalid attributes

Author: rwinch

framework-docs/modules/ROOT/pages/web/web-uris.adoc

@@ -1,4 +1,3 @@
-[id={chapter}.web-uricomponents]
 [[uricomponents]]
 = UriComponents
 [.small]#Spring MVC and Spring WebFlux#
@@ -102,12 +101,11 @@ You can shorten it further still with a full URI template, as the following exam
 
 
 
-[id={chapter}.web-uribuilder]
 [[uribuilder]]
 = UriBuilder
 [.small]#Spring MVC and Spring WebFlux#
 
-<<{chapter}.web-uricomponents, `UriComponentsBuilder`>> implements `UriBuilder`. You can create a
+<<web-uricomponents, `UriComponentsBuilder`>> implements `UriBuilder`. You can create a
 `UriBuilder`, in turn, with a `UriBuilderFactory`. Together, `UriBuilderFactory` and
 `UriBuilder` provide a pluggable mechanism to build URIs from URI templates, based on
 shared configuration, such as a base URL, encoding preferences, and other details.
@@ -195,7 +193,6 @@ that holds configuration and preferences, as the following example shows:
 ----
 
 
-[id={chapter}.web-uri-encoding]
 [[uri-encoding]]
 = URI Encoding
 [.small]#Spring MVC and Spring WebFlux#

framework-docs/modules/ROOT/pages/web/webflux/ann-rest-exceptions.adoc

@@ -76,7 +76,7 @@ to customize the problem details for Spring WebFlux exceptions. This is supporte
 - Each `ErrorResponse` exposes a message code and arguments to resolve the "detail" field
 through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource].
 The actual message code value is parameterized with placeholders, e.g.
-`"HTTP method {0} not supported"` to be expanded from the arguments.
+`+"HTTP method {0} not supported"+` to be expanded from the arguments.
 - Each `ErrorResponse` also exposes a message code to resolve the "title" field.
 - `ResponseEntityExceptionHandler` uses the message code and arguments to resolve the
 "detail" and the "title" fields.
@@ -93,41 +93,41 @@ arguments and codes for Spring WebFlux exceptions:
 
 | `UnsupportedMediaTypeStatusException`
 | (default)
-| `{0}` the media type that is not supported, `{1}` list of supported media types
+| `+{0}+` the media type that is not supported, `+{1}+` list of supported media types
 
 | `UnsupportedMediaTypeStatusException`
 | (default) + ".parseError"
 |
 
 | `MissingRequestValueException`
 | (default)
-| `{0}` a label for the value (e.g. "request header", "cookie value", ...), `{1}` the value name
+| `+{0}+` a label for the value (e.g. "request header", "cookie value", ...), `+{1}+` the value name
 
 | `UnsatisfiedRequestParameterException`
 | (default)
-| `{0}` the list of parameter conditions
+| `+{0}+` the list of parameter conditions
 
 | `WebExchangeBindException`
 | (default)
-| `{0}` the list of global errors, `{1}` the list of field errors.
+| `+{0}+` the list of global errors, `+{1}+` the list of field errors.
 Message codes and arguments for each error within the `BindingResult` are also resolved
 via `MessageSource`.
 
 | `NotAcceptableStatusException`
 | (default)
-| `{0}` list of supported media types
+| `+{0}+` list of supported media types
 
 | `NotAcceptableStatusException`
 | (default) + ".parseError"
 |
 
 | `ServerErrorException`
 | (default)
-| `{0}` the failure reason provided to the class constructor
+| `+{0}+` the failure reason provided to the class constructor
 
 | `MethodNotAllowedException`
 | (default)
-| `{0}` the current HTTP method, `{1}` the list of supported HTTP methods
+| `+{0}+` the current HTTP method, `+{1}+` the list of supported HTTP methods
 
 |===
 

framework-docs/modules/ROOT/pages/web/webmvc/mvc-ann-rest-exceptions.adoc

@@ -76,7 +76,7 @@ to customize the problem details for Spring MVC exceptions. This is supported as
 - Each `ErrorResponse` exposes a message code and arguments to resolve the "detail" field
 through a xref:core/beans/context-introduction.adoc#context-functionality-messagesource[MessageSource].
 The actual message code value is parameterized with placeholders, e.g.
-`"HTTP method {0} not supported"` to be expanded from the arguments.
+`+"HTTP method {0} not supported"+` to be expanded from the arguments.
 - Each `ErrorResponse` also exposes a message code to resolve the "title" field.
 - `ResponseEntityExceptionHandler` uses the message code and arguments to resolve the
 "detail" and the "title" fields.
@@ -97,19 +97,19 @@ arguments and codes for Spring MVC exceptions:
 
 | `ConversionNotSupportedException`
 | (default)
-| `{0}` property name, `{1}` property value
+| `+{0}+` property name, `+{1}+` property value
 
 | `HttpMediaTypeNotAcceptableException`
 | (default)
-| `{0}` list of supported media types
+| `+{0}+` list of supported media types
 
 | `HttpMediaTypeNotAcceptableException`
 | (default) + ".parseError"
 |
 
 | `HttpMediaTypeNotSupportedException`
 | (default)
-| `{0}` the media type that is not supported, `{1}` list of supported media types
+| `+{0}+` the media type that is not supported, `+{1}+` list of supported media types
 
 | `HttpMediaTypeNotSupportedException`
 | (default) + ".parseError"
@@ -125,49 +125,49 @@ arguments and codes for Spring MVC exceptions:
 
 | `HttpRequestMethodNotSupportedException`
 | (default)
-| `{0}` the current HTTP method, `{1}` the list of supported HTTP methods
+| `+{0}+` the current HTTP method, `+{1}+` the list of supported HTTP methods
 
 | `MethodArgumentNotValidException`
 | (default)
-| `{0}` the list of global errors, `{1}` the list of field errors.
+| `+{0}+` the list of global errors, `+{1}+` the list of field errors.
   Message codes and arguments for each error within the `BindingResult` are also resolved
   via `MessageSource`.
 
 | `MissingRequestHeaderException`
 | (default)
-| `{0}` the header name
+| `+{0}+` the header name
 
 | `MissingServletRequestParameterException`
 | (default)
-| `{0}` the request parameter name
+| `+{0}+` the request parameter name
 
 | `MissingMatrixVariableException`
 | (default)
-| `{0}` the matrix variable name
+| `+{0}+` the matrix variable name
 
 | `MissingPathVariableException`
 | (default)
-| `{0}` the path variable name
+| `+{0}+` the path variable name
 
 | `MissingRequestCookieException`
 | (default)
-| `{0}` the cookie name
+| `+{0}+` the cookie name
 
 | `MissingServletRequestPartException`
 | (default)
-| `{0}` the part name
+| `+{0}+` the part name
 
 | `NoHandlerFoundException`
 | (default)
 |
 
 | `TypeMismatchException`
 | (default)
-| `{0}` property name, `{1}` property value
+| `+{0}+` property name, `+{1}+` property value
 
 | `UnsatisfiedServletRequestParameterException`
 | (default)
-| `{0}` the list of parameter conditions
+| `+{0}+` the list of parameter conditions
 
 |===
 

framework-docs/modules/ROOT/pages/web/websocket-intro.adoc

@@ -1,4 +1,3 @@
-[id={chapter}.websocket-intro]
 [[introduction-to-websocket]]
 = Introduction to WebSocket
 
@@ -55,7 +54,6 @@ instructions of the cloud provider related to WebSocket support.
 
 
 
-[id={chapter}.websocket-intro-architecture]
 [[http-versus-websocket]]
 == HTTP Versus WebSocket
 
@@ -82,7 +80,6 @@ In the absence of that, they need to come up with their own conventions.
 
 
 
-[id={chapter}.websocket-intro-when-to-use]
 [[when-to-use-websockets]]
 == When to Use WebSockets