Consistency in case and terminology

[ciseng]

Daniel Migault: Section 1.3 defines the Topic name. It might be more helpful to the reader if the exact same term is used both in the text of the document and in the terminology - that is even considering upper/lower letters.  

I am wondering if the broker should be defined as well. 

Similarly, there seems that Clients are composed of various sub-clients ( client authorisation server, the client (MQTT), subscriber, publisher). Maybe these different designations could be defined as well in the terminology section. Maybe also some designations might not be necessary to introduce. 

Cigdem Sengul: Yes, we assumed there may be a CAS that will speak HTTPS to get the tokens from AS. OR if the client itself is capable of doing that, it would not need a CAS.

Other than that, the MQTT client software may act both as a publisher or subscriber. We only separated them for the clarity of presentation. Also, there are some command line MQTT clients that just publish or just subscribe. Still, I would not consider publisher/subscriber pieces as sub-clients. I think we explain this in the text but will bring it to the Terminology section.

[ciseng]

Daniel Migault: Figure mentions Will Flag while the text mentions Will flag. 

[ciseng]

• Improved consistency in the use of terminology, and upper/lower case
• Defined Broker
• Removed ref. actors document and clarified the client authorization server etc.