@code{method}, @code{signal}, and @code{property} elements. Unlike
properties, which can change their values during lifetime of a D-Bus
object, annotations are static. Often they are used for code
-generators of D-Bus langugae bindings. Example:
+generators of D-Bus language bindings. Example:
@example
<annotation name="de.berlios.Pinot.GetStatistics" value="pinotDBus"/>
@node Methods and Signal
@section Applying the functionality.
-Methods and signals are the communicatione means to D-Bus. The
+Methods and signals are the communication means to D-Bus. The
following functions return their specifications.
@defun dbus-introspect-get-method-names bus service path interface
@defvar dbus-event-error-hooks
This hook variable keeps a list of functions, which are called when a
D-Bus error happens in the event handler. Every function must accept
-two arguments, the event and the error variable catched in
+two arguments, the event and the error variable caught in
@code{condition-case} by @code{dbus-error}.
Such functions can be used the adapt the error signal to be raised.