From aa3b094b75248f6e8d29395dc46a980fdb670c4d Mon Sep 17 00:00:00 2001
From: Anders Svensson
Date: Wed, 29 Aug 2012 18:18:58 +0200
Subject: Minor updates/corrections to Users Guide
---
lib/diameter/doc/src/diameter_examples.xml | 3 +--
lib/diameter/doc/src/diameter_intro.xml | 27 ++++++++++++++-------------
lib/diameter/doc/src/diameter_using.xml | 4 ++--
3 files changed, 17 insertions(+), 17 deletions(-)
(limited to 'lib/diameter/doc')
diff --git a/lib/diameter/doc/src/diameter_examples.xml b/lib/diameter/doc/src/diameter_examples.xml
index 966d1f1eee..1fd7755695 100644
--- a/lib/diameter/doc/src/diameter_examples.xml
+++ b/lib/diameter/doc/src/diameter_examples.xml
@@ -5,7 +5,7 @@
-A Diameter peer is implemented by configuring a service and
+A Diameter node is implemented by configuring a service and
one or more transports using the interface module
diameter.
The service configuration defines the Diameter applications to be
-supported by the peer and, typically, the capabilities that it should
+supported by the node and, typically, the capabilities that it should
send to remote peers at capabilities exchange upon the establishment
of transport connections.
A transport is configured on a service and provides protocol-specific
@@ -57,16 +57,17 @@ diameter and implemented by a transport module.
The diameter application provides two transport modules: diameter_tcp and diameter_sctp for transport over TCP
-(using gen_tcp) and SCTP (using gen_sctp) respectively.
+(using gen_tcp) and SCTP
+(using gen_sctp) respectively.
Other transports can be provided by any module that implements
diameter's transport
interface.
-While a service typically implements a single Diameter peer (as
+While a service typically implements a single Diameter node (as
identified by an Origin-Host AVP), transports can themselves be
-associated with capabilities AVP's so that a single service be used to
-implement more than one Diameter peer.
+associated with capabilities AVP's so that a single service can be
+used to implement more than one Diameter node.
Each Diameter application defined on a service is configured with a
@@ -76,19 +77,19 @@ diameter communicates the connectivity of remote peers, requests peer
selection for outgoing requests, and communicates the reception of
incoming Diameter request and answer messages.
An application using diameter implements these application callback
-modules to provide the functionality of the Diameter peer(s) it
+modules to provide the functionality of the Diameter node(s) it
implements.
-Each Diameter application is also configured with one or more
-dictionary modules
+Each Diameter application is also configured with a
+dictionary module
that provide encode/decode functionality for outgoing/incoming
-Diameter messages.
-A module is generated from a specification file using the diameterc utility.
Dictionaries for the RFC 3588 Diameter Common Messages, Base
-Accounting and Relay applications are provided by the diameter
+Accounting and Relay applications are provided with the diameter
application.
diff --git a/lib/diameter/doc/src/diameter_using.xml b/lib/diameter/doc/src/diameter_using.xml
index 809b76bdf3..7d9c0cd492 100644
--- a/lib/diameter/doc/src/diameter_using.xml
+++ b/lib/diameter/doc/src/diameter_using.xml
@@ -5,7 +5,7 @@
-2011
+20112012
Ericsson AB. All Rights Reserved.
@@ -23,7 +23,7 @@ under the License.
-Using the stack
+Usage
--
cgit v1.2.3