Changes: Language corrections into documentation

RevBy:TrustMe

debian/changelog

@@ -1,6 +1,7 @@
 applauncherd (0.30.6) unstable; urgency=low
 
-  * 
+  * Changes: Performance test modified. Tracking pixel co-ordinates changed.
+  * Changes: Language corrections into documentation.
 
  -- Alexey Shilov <alexey.shilov@nokia.com>  Tue, 28 Jun 2011 13:55:48 +0300
 

doc/debug.dox

@@ -2,9 +2,9 @@
 
 \section debugging Debugging
 
-To debug a launched application, the debugger must be attached
-to an already running booster process. Due to security limitations
-it's required to use \c aegis-su tool from \c aegis-dss-tools package. 
+To debug a launched application, the debugger must be attached to an
+already running booster process. Due to security limitations, it is
+required to use \c aegis-su tool from \c aegis-dss-tools package. 
 For instance:
 
 1. Run the following command:

doc/libmeegotouchboost.dox

@@ -43,14 +43,14 @@ M_EXPORT int main(int argc, char **argv)
 }
 \endcode
 
-If your application loads a plugin that needs to access some symbols
+If your application loads a plug-in that needs to access some symbols
 in the main application, the symbols also need to be exported. In
-addition, the \c --global-syms invoker parameter needs to use, as
-described in \ref invokerparameters "Advanced Invoker Command Line Parameters".
+addition, you must use the \c --global-syms invoker parameter, as
+described in \ref invokerparameters "Advanced invoker command line parameters".
 
 Normally you do not need to worry about the compiler and linker
 flags, as the \c libmeegotouch-dev package provides configuration
-options for \c QMake, \c cmake, and \c pkg-config. If you are building
+options for \c qmake, \c CMake, and \c pkg-config. If you are building
 a Debian package, make your package build-depend on \c
 libmeegotouch-dev and your application binary package depend on 
 \c applauncherd.

doc/limitations.dox

@@ -111,13 +111,14 @@ Splash screen functionality needs support from the \c mcompositor window manager
 
 \section wm_class_value WM_CLASS value
 
-If application is started with m-booster but it creates its own MApplicationWindow based object 
-(e.g. MApplicationWindow derived class object or application has multiple windows), 
-current launcher implementation does not set correct value for WM_CLASS property of X window.
-WM_CLASS property is used e.g. by Compositor as application name to notify user when application
-gets stuck. 
- 
-Application should set correct WM_CLASS property by following way:
+If an application is started with m-booster but it creates its own
+MApplicationWindow based object, such as an MApplicationWindow derived
+class object, or if an application has multiple windows, the launcher
+does not currently set the correct value for WM_CLASS property of X
+window. The WM_CLASS property is used, for example, by Compositor as
+the application name to notify the user if the application is stuck.
+
+Set the WM_CLASS property for the application as follows:
 
 \code
 M_EXPORT int main(int argc, char **argv)

doc/mdeclarativecache_mainpage.dox

@@ -12,7 +12,8 @@
   </table>
  
 \section getting_started Getting started
-  For writing application which are using MDeclarativeCache, please see the full 
-  developer guide from applauncher-doc package.  
-  
+  For writing applications which are using MDeclarativeCache, please see the full 
+  developer guide "Optimising application startup" in "Best practices for 
+  application development" section.
+
 */

doc/qmlboost.dox

@@ -38,14 +38,15 @@ visible. This can be done as follows:
   }
 \endcode
 
-If your application loads a plugin that needs to access some symbols
+
+If your application loads a plug-in that needs to access some symbols
 in the main application, the symbols also need to be exported. In
-addition, the \c --global-syms invoker parameter needs to use, as
-described in \ref invokerparameters "Advanced Invoker Command Line Parameters".
+addition, you must use the \c --global-syms invoker parameter, as
+described in \ref invokerparameters "Advanced invoker command line parameters".
 
 Normally you do not need to worry about the compiler and linker
 flags, as the \c applauncherd-dev package provides configuration
-options for \c QMake, \c cmake, and \c pkg-config. If you are building
+options for \c qmake, \c CMake, and \c pkg-config. If you are building
 a Debian package, make your package build-depend on \c
 applauncherd-dev and your application binary package depend on
 \c applauncherd.

doc/qtboost.dox

@@ -38,12 +38,13 @@ visible. This can be done as follows:
   }
 \endcode
 
-If your application loads a plugin that needs to access some symbols
+
+If your application loads a plug-in that needs to access some symbols
 in the main application, the symbols also need to be exported. In
-addition, the \c --global-syms invoker parameter needs to use, as
-described in \ref invokerparameters "Advanced Invoker Command Line Parameters".
+addition, you must use the \c --global-syms invoker parameter, as
+described in \ref invokerparameters "Advanced invoker command line parameters".
 
-Normally you should not need to worry about the compiler and linker
+Normally you do not need to worry about the compiler and linker
 flags, as the \c applauncherd-dev package provides configuration
 options for \c qmake, \c CMake, and \c pkg-config. If you are building
 a Debian package, make your package build-depend on \c

doc/singleinstance.dox

@@ -19,11 +19,12 @@ As a result, a lock file
 If applauncherd cannot acquire the lock, it tries to find the corresponding
 window and activates it. 
 
-Single-instance functionality requires that the shown window belongs to the invoked
-application binary. For example if the invoked application starts a new application 
-as a plugin and the plugin shows the window, single-instance could be used only if 
-plugin's window XProperty WM_COMMAND is manually set to correspond with the application
-name used in the single-instance lock file.
+Using single instance support requires that the shown window belongs
+to the invoked application binary. For example, if the invoked
+application starts a new application as a plug-in and the plug-in
+shows the window, you must manually set the plug-in window XProperty
+WM_COMMAND. To use single instance support, set the property to
+correspond with the application name used in the single instance lock file.
 
 Consider using --single-instance instead of the single instance functionality
 provided by D-Bus, because --single-instance is much faster in most cases.