[anjuta] Fix typos in manuals
- From: Sebastien Granjoux <sgranjoux src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [anjuta] Fix typos in manuals
- Date: Wed, 25 Mar 2015 21:05:21 +0000 (UTC)
commit e4157aaa5973c9726f0cba2195bfe0c8e927fe34
Author: Anders Jonsson <anders jonsson norsjovallen se>
Date: Tue Mar 24 23:31:08 2015 +0100
Fix typos in manuals
manuals/anjuta-manual/C/anjuta-code-assist.page | 2 +-
.../anjuta-manual/C/anjuta-code-indentation.page | 4 ++--
.../anjuta-manual/C/autotools-build-plugin.page | 2 +-
.../C/autotools-project-target-type.page | 8 ++++----
.../C/project-manager-module-new.page | 2 +-
manuals/anjuta-manual/C/project-manager.page | 2 +-
.../reference/libanjuta/anjuta-architecture.sgml | 4 ++--
.../libanjuta/plugin-description-file.sgml | 2 +-
manuals/reference/libanjuta/writing-plugins.sgml | 6 +++---
9 files changed, 16 insertions(+), 16 deletions(-)
---
diff --git a/manuals/anjuta-manual/C/anjuta-code-assist.page b/manuals/anjuta-manual/C/anjuta-code-assist.page
index c84b886..d1d5098 100644
--- a/manuals/anjuta-manual/C/anjuta-code-assist.page
+++ b/manuals/anjuta-manual/C/anjuta-code-assist.page
@@ -22,7 +22,7 @@
<p>Autocompletion automatically suggests functions and other code symbols after
you start typing by trying to match existing symbols with the first characters typed.
It will popup a drop-down menu where you can select a match by using the
-<key>Enter</key> key. Normally this happens automaticly after you typed the third
+<key>Enter</key> key. Normally this happens automatically after you typed the third
(non-whitespace) character but you can also
force it by using the <guiseq><gui>Edit</gui><gui>Auto-Complete</gui></guiseq>
menu item.
diff --git a/manuals/anjuta-manual/C/anjuta-code-indentation.page
b/manuals/anjuta-manual/C/anjuta-code-indentation.page
index fc86f68..edd297b 100644
--- a/manuals/anjuta-manual/C/anjuta-code-indentation.page
+++ b/manuals/anjuta-manual/C/anjuta-code-indentation.page
@@ -35,7 +35,7 @@ if different styles used in the same files. For a better solution, see
the next section.</p>
<note>
-<p>Unless explicitely changed in the preferences the indentation settings found
+<p>Unless explicitly changed in the preferences the indentation settings found
in the Modeline of a file will be used instead of the
configured settings to keep the file consistent.</p>
</note>
@@ -58,7 +58,7 @@ many developers work on the same project and use different environments.</p>
<section>
<title>Indenting blocks of code</title>
-<p>Normally new lines are approprietely indented automatically but you can
+<p>Normally new lines are appropriately indented automatically but you can
indent existing lines or all selected code with the
<guiseq><gui>Edit</gui><gui>Auto-Indent</gui></guiseq> menu item.</p>
diff --git a/manuals/anjuta-manual/C/autotools-build-plugin.page
b/manuals/anjuta-manual/C/autotools-build-plugin.page
index 16a60f3..ce3eb98 100644
--- a/manuals/anjuta-manual/C/autotools-build-plugin.page
+++ b/manuals/anjuta-manual/C/autotools-build-plugin.page
@@ -46,7 +46,7 @@
</item>
<item>
<title><cmd>make dist</cmd></title>
- <p>Use to build a distributation package, called only in the project directory.</p>
+ <p>Use to build a distribution package, called only in the project directory.</p>
</item>
</terms>
diff --git a/manuals/anjuta-manual/C/autotools-project-target-type.page
b/manuals/anjuta-manual/C/autotools-project-target-type.page
index 99997cd..af39692 100644
--- a/manuals/anjuta-manual/C/autotools-project-target-type.page
+++ b/manuals/anjuta-manual/C/autotools-project-target-type.page
@@ -30,7 +30,7 @@
<item>
<title>Module (Libtool)</title>
<p>It represents a library, often named a plugin, linked at run time
- explicitely by the program itself.
+ explicitly by the program itself.
It is used to only load the code corresponding to the used features.</p>
<p>It uses the Libtool package. Its name does not need the 'lib'
prefix but must have the '.la' extension.</p>
@@ -44,7 +44,7 @@
</item>
<item>
<title>Program</title>
- <p>It represents compiled program by example from C souces files.
+ <p>It represents compiled program by example from C source files.
All children represent the source files compiled to generate the
program.</p>
</item>
@@ -54,11 +54,11 @@
</item>
<item>
<title>Java module</title>
- <p>It represents a progran written in Java.</p>
+ <p>It represents a program written in Java.</p>
</item>
<item>
<title>LISP module</title>
- <p>It represents a progran written in LISP.</p>
+ <p>It represents a program written in LISP.</p>
</item>
<item>
<title>Header files</title>
diff --git a/manuals/anjuta-manual/C/project-manager-module-new.page
b/manuals/anjuta-manual/C/project-manager-module-new.page
index 2a99cd9..c7b871f 100644
--- a/manuals/anjuta-manual/C/project-manager-module-new.page
+++ b/manuals/anjuta-manual/C/project-manager-module-new.page
@@ -55,7 +55,7 @@
</item>
<item>
<p>It could be that the library is not packaged, it is often the
- case for libraries not developped on Linux. See the chapter
+ case for libraries not developed on Linux. See the chapter
<link xref="project-manager-library-add"/> explaining how to
use them.</p>
</item>
diff --git a/manuals/anjuta-manual/C/project-manager.page b/manuals/anjuta-manual/C/project-manager.page
index f52aabd..611f36b 100644
--- a/manuals/anjuta-manual/C/project-manager.page
+++ b/manuals/anjuta-manual/C/project-manager.page
@@ -27,7 +27,7 @@
</p>
<p>
- The project backend to use is choosen when creating or importing a new
+ The project backend to use is chosen when creating or importing a new
project in <app>Anjuta</app>. It is displayed in the properties of the
project root node and can be changed at any time.
</p>
diff --git a/manuals/reference/libanjuta/anjuta-architecture.sgml
b/manuals/reference/libanjuta/anjuta-architecture.sgml
index e6da98d..ada1b5f 100644
--- a/manuals/reference/libanjuta/anjuta-architecture.sgml
+++ b/manuals/reference/libanjuta/anjuta-architecture.sgml
@@ -5,7 +5,7 @@
its core is the shell
(<link linkend="AnjutaShell"><type>AnjutaShell</type></link>)
in which all plugins are loaded. Plugins can also merge
- thier UI and preferences in
+ their UI and preferences in
<link linkend="AnjutaUI"><type>AnjutaUI</type></link>
and
<link linkend="AnjutaPreferences"><type>AnjutaPreferences</type></link>,
@@ -14,7 +14,7 @@
<para>
Plugins subclass <link linkend="AnjutaPlugin"><type>AnjutaPlugin</type></link>
abstract class and interact with each other using predefined interfaces.
- They can also export objects with <emphasis>Values Sytem</emphasis> in
+ They can also export objects with <emphasis>Values System</emphasis> in
<link linkend="AnjutaShell"><type>AnjutaShell</type></link>.
</para>
<para>
diff --git a/manuals/reference/libanjuta/plugin-description-file.sgml
b/manuals/reference/libanjuta/plugin-description-file.sgml
index e3d99ac..01e2126 100644
--- a/manuals/reference/libanjuta/plugin-description-file.sgml
+++ b/manuals/reference/libanjuta/plugin-description-file.sgml
@@ -45,7 +45,7 @@
<para>
Comma separated list
of all interfaces that this plugin depends on. Plugin
- implementing these interaces will be activated before
+ implementing these interfaces will be activated before
activating this plugin. This field is optional. If
there is no dependencies, it may not present.
</para>
diff --git a/manuals/reference/libanjuta/writing-plugins.sgml
b/manuals/reference/libanjuta/writing-plugins.sgml
index cec2161..8c60561 100644
--- a/manuals/reference/libanjuta/writing-plugins.sgml
+++ b/manuals/reference/libanjuta/writing-plugins.sgml
@@ -5,7 +5,7 @@
<xref linkend="anjuta-architecture"/>
to get a picture of how plugins interact with Anjuta shell and other
plugins. Only a general overview is necessary for now. Eventually, as
- we procceed through this article, you can visit respective sections
+ we proceed through this article, you can visit respective sections
to read more.
This is a tutorial style article and is never meant to be a cover-all
document. You should read other relevent documents linked at respective
@@ -222,7 +222,7 @@ static gpointer parent_class;
</para>
<para>
We have one action in our plugin and here is the callback for that.
- In this function, we are quering
+ In this function, we are querying
<link linkend="AnjutaShell"><type>AnjutaShell</type></link>
for a plugin implementing
<link linkend="IAnjutaDocumentManager"><type>IAnjutaDocumentManager</type></link>
@@ -230,7 +230,7 @@ static gpointer parent_class;
to see if it implements
<link linkend="IAnjutaFile"><type>IAnjutaFile</type></link>
interface,
- using which we deternime filename of currently active editor. If
+ using which we determine filename of currently active editor. If
the editor doesn't support
<link linkend="IAnjutaFile"><type>IAnjutaFile</type></link>
interface, we show an error dialog.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]