Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
When a client creates a registry object, the registry object
will emit a global event for each global currently in the
- regitry. Globals come and go as a result of device hotplugs,
+ registry. Globals come and go as a result of device hotplugs,
reconfiguration or other events, and the registry will send out
@global and @global_remove events to keep the client up to date
with the changes. To mark the end of the initial burst of
* \return 0 on success or -1 on failure
*
* Set proxy's listener to \c implementation and its user data to
- * \c data. Ifa listener has already been set, this functions
+ * \c data. If a listener has already been set, this function
* fails and nothing is changed.
*
* \c implementation is a vector of function pointers. For an opcode
- * \c n, \c implemention[n] should point to the handler of \c n for
+ * \c n, \c implementation[n] should point to the handler of \c n for
* the given object.
*
* \memberof wl_proxy