Spec: be clearer about what activation means

The spec previously mentioned that CORBA calls this activation, but
did not explicitly say that D-Bus has copied this jargon term.
It's 2016, and developers are probably more likely to be familiar
with D-Bus than with CORBA at this point: explicitly say that *our*
jargon term for this action is activation.

Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: Philip Withnall <philip.withnall@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=98671

1 files changed, 5 insertions, 3 deletions

diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
index 64f561b3..61993969 100644
--- a/doc/dbus-specification.xml
+++ b/doc/dbus-specification.xml
@@ -4970,12 +4970,14 @@
       </sect3>
     </sect2>
     <sect2 id="message-bus-starting-services">
-      <title>Message Bus Starting Services</title>
+      <title>Message Bus Starting Services (Activation)</title>
       <para>
         The message bus can start applications on behalf of other applications.
-        In CORBA terms, this would be called <firstterm>activation</firstterm>.
+        This is referred to as <firstterm>service activation</firstterm> or
+        <firstterm>activation</firstterm>.
         An application that can be started in this way is called a
-        <firstterm>service</firstterm>.
+        <firstterm>service</firstterm> or an
+        <firstterm>activatable service</firstterm>.
       </para>
       <para>
         With D-Bus, starting a service is normally done by name. That is,