Fixed a typo:

-                the 'reaching node' and the 'reporting node' do not need
+                the 'reacting node' and the 'reporting node' do not need

Added the implicit learning of app-id and server-id into OC-OLR AVP text:

+               <t>The OC-OLR AVP does not contain explicit information to which
+                application it applies to and who inserted the AVP or whom the
+                specific OC-OLR AVP concerns to. Both these information is implicitly
+                learned from the encapsulating Diameter message/command. The application
+                the OC-OLR AVP applies to is the same as the Application-Id found in the
+                Diameter message header. The identity the OC-OLR AVP concerns is
+                determined from the Origin-Host AVP found from the encapsulating Diameter
+                command.
+               </t>

Removed the trouble making sentence:

-           server farm of real Diameter servers. Such network topologies imply
-           that the Diameter agents in front of servers remain in the Diameter
-           signaling path for all the messages related to the same session or
-           user.
-          </t>
-          <t>
-           [OpenIssue: How is the last sentence relevant?]

Changed the title to DOIC:

-    <title abbrev='Diameter Overload Indication'>Diameter Overload Indication</title>
+    <title abbrev='DOIC'>Diameter Overload Indication Conveyance</title>

-           In the context of the Diameter Overload Indication dissemination
+           In the context of the Diameter Overload Indication Conveyance (DOIC)

-      <t>
-       [OpenIssue: Is DOC the best choice for an acronym? That has some
-       confusing collisions with 'doc' as document, and will be almost
-       impossible to google for. Perhaps Diameter Overload Indication (DOI) or
-       Diameter Overload Indication Conveyance (DOIC)?]
-      </t>

Signed-off-by: Jouni Korhonen <jouni.korhonen@broadcom.com>