reformat

modules/feed-comm/feed-comm-api/README.adoc

@@ -8,14 +8,20 @@ If your client is Java, you can use the Java API that also comes with the artifa
 
 Because this API flows over WebSockets, multiple requests and responses may be sent and received to clients. Because of this, in order to make it easier on the client to deserialize incoming requests and responses, the messages that flow over the WebSocket connection are not merely the JSON-encoded data. Instead, the JSON-encoded data is prefixed with the name of the schema, optionally prefixed with the package name. For example, suppose NotificationMessage schema results in a JSON of the form:
 
-{noformat}{"message": "the msg here"}{noformat}
+----
+{"message":"the msg here"}
+----
 
 The client receiving this message will actually receive the following data:
 
-{noformat}NotificationMessage={"message": "the msg here"}{noformat}
+----
+NotificationMessage={"message":"the msg here"}
+----
 
 It may optionally look like:
 
-{noformat}org.hawkular.feedcomm.api.NotificationMessage={"message": "the msg here"}{noformat}
+----
+org.hawkular.feedcomm.api.NotificationMessage={"message":"the msg here"}
+----
 
 A Java client can use the utility org.hawkular.feedcomm.api.ApiDeserializer.deserialize() (passing in that string) to obtain the Java POJO that represents this notification message. A non-Java client can utilize the NotificationMessage.schema.json (note, the name of the schema is the same name as that prefix, minus any optional package name) in order to know how to deserialize the JSON message.