[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdevelop/doc/kdevelop
From:       Mario Scalas <mario.scalas () libero ! it>
Date:       2003-07-01 21:09:20
[Download RAW message or body]

CVS commit by marios: 

Fixed spelling errors (thanks to Raphael Langerhorst).


  M +4 -4      index.docbook   1.14


--- kdevelop/doc/kdevelop/index.docbook  #1.13:1.14
@@ -429,5 +429,5 @@
 The distribution of your applications does not require the end-user to have anything \
different installed  other than a C++ compiler and the appropriate development \
                libraries, which is most often the case; but
-ou can as well distribut binary packages of your application.  In either way, the \
end-user of your product +you can as well distribute binary packages of your \
application.  In either way, the end-user of your product  does not have to have \
&kdevelop; installed.  For giving away your sources, we advise to include the   \
project file of &kdevelop; as well, as this makes it very easy for other developerss \
to work with your @@ -972,5 +972,5 @@
 This view is shown on the left side of the main window and contains a linear
 list of all classes, variables and functions in your project. It is designed
-as a tree view. If you open a class node by clicking on bit, a list with all 
+as a tree view. If you open a class node by clicking on it, a list with all
 methods and attributes of the respective class is shown.
 </para>
@@ -1511,5 +1511,5 @@
 application, where often code is only loaded on demand as a plugin (using
 the libc function <function>dlopen(3)</function>), this can be incovenient. 
-Therefore, &kdevelop; rolls it own support for breakpoints in shared 
+Therefore, &kdevelop; rolls its own support for breakpoints in shared
 libraries. If you set this option, it allows you to set breakpoints in 
 libraries which are not loaded. Then, whenever <application>gdb</application>
@@ -1633,5 +1633,5 @@
 users into your working directory. When you use this menu item over
 a directory, the update normally happens recursively, except if you
-have disable this in the configuration file <filename>.cvsrc</filename>.
+have disabled this in the configuration file <filename>.cvsrc</filename>.
 </para>
 </formalpara>


[prev in list] [next in list] [prev in thread] [next in thread]