summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorluzpaz <luzpaz@users.noreply.github.com>2017-11-14 17:39:57 +0000
committerluzpaz <luzpaz@users.noreply.github.com>2017-11-14 17:39:57 +0000
commit5519c60577390971e2e3a2b3bc1af3895d97860b (patch)
treea98379727cf621f8a68019ca83868d4c1f283e10 /doc
parentDon't set a default 'font-size' when copying text if one is not set. (diff)
downloadinkscape-5519c60577390971e2e3a2b3bc1af3895d97860b.tar.gz
inkscape-5519c60577390971e2e3a2b3bc1af3895d97860b.zip
Misc. Typo fixes
Follow up to #119
Diffstat (limited to 'doc')
-rw-r--r--doc/LOGGING.txt2
-rw-r--r--doc/extension_system.txt2
-rw-r--r--doc/extension_system.xml8
-rw-r--r--doc/nr-filter-interface.txt4
4 files changed, 8 insertions, 8 deletions
diff --git a/doc/LOGGING.txt b/doc/LOGGING.txt
index a6b9314df..0fa90e1da 100644
--- a/doc/LOGGING.txt
+++ b/doc/LOGGING.txt
@@ -1,7 +1,7 @@
Logging Inkscape events can be done by switching on DEBUG logs:
-Set the enviroment variables:
+Set the environment variables:
INKSCAPE_DEBUG_LOG=filename.xml
INKSCAPE_DEBUG_FILTER=Comma,List,Options
diff --git a/doc/extension_system.txt b/doc/extension_system.txt
index 12c3ebb97..0fad8f336 100644
--- a/doc/extension_system.txt
+++ b/doc/extension_system.txt
@@ -234,7 +234,7 @@ An input extension provides a way to get data into Inkscape. This type
of extension creates a document given a filename. This is done by using
the 'open' method within the class. Also, there is a 'prefs' function
which will generate a GtkDialog. This dialog is then used to get any
-settings that the incomming file and extension my use. This function is
+settings that the incoming file and extension may use. This function is
executed, and the dialog returns, before the open method is called.
There are also several other settings stored in an Input extension.
diff --git a/doc/extension_system.xml b/doc/extension_system.xml
index e4271362a..dc6d25ecc 100644
--- a/doc/extension_system.xml
+++ b/doc/extension_system.xml
@@ -6,7 +6,7 @@
<title>Introduction</title>
<para>The extensions system in Inkscape is a way for adding functionality to Inkscape, without affecting the core of the program itself. We want Inkscape to follow a core-plus-modules approach similar to that adopted by many successful open source projects such as the Linux kernel, Perl, Apache, Gimp, and so on. There are many different types of extension mechanisms, including file format conversion tools, filter scripts that process SVG, user interface elements that can be added at runtime, and so forth.</para>
<para>This proposal defines a design for handling this wide variety of extensions in a flexible manner. This document provides a way to understand the extensions system, and how extensions fit into this overall system.</para>
- <para>Much of the documentation that will be useful for users of the extension system is not included in this document, it is autogenerated from the source code and placed on the Inkscape webpage. While this is less convienient, it is more correct, and maintained as the source code is modified. Please look aton the Inkscape webpage also.</para>
+ <para>Much of the documentation that will be useful for users of the extension system is not included in this document, it is autogenerated from the source code and placed on the Inkscape webpage. While this is less convenient, it is more correct, and maintained as the source code is modified. Please look aton the Inkscape webpage also.</para>
</chapter>
<chapter>
<title>Terminology</title>
@@ -118,7 +118,7 @@
<variablelist>
<varlistentry>
<term>ID</term>
- <para>A unique identifier for this extension that is used for refering to the extension and naming its parameters in the configuration files.</para>
+ <para>A unique identifier for this extension that is used for referring to the extension and naming its parameters in the configuration files.</para>
</varlistentry>
<varlistentry>
<term>Name</term>
@@ -153,8 +153,8 @@
<para>Each Extension is identified by it's 'Type'. This determines the type of programmatic interface that it adheres to, enabling Inkscape to know what functionality it can expect from the extension.</para>
<section>
<title>Input</title>
- <para>An input extension provides a way to get data into Inkscape. This type of extension creates a document given a filename. This is done by using the 'open' method within the class. Also, there is a 'prefs' function which will generate a GtkDialog. This dialog is then used to get any settings that the incomming file and extension my use. This function is executed, and the dialog returns, before the open method is called.</para>
- <para>There are also several other settings stored in an Input extension. This includes information on the type of file the input module can take in including its filename extension and mime type. Also, there is a space to store a tooltip for additional information on the file type in the file dialog. Lastly, there is the key of which Output extension is recommended for saving this filetype. This is useful, as there is no other direct links between the Input and Ouput functions, and a user expects to be able to open and save without using the 'Save As...' dialog.</para>
+ <para>An input extension provides a way to get data into Inkscape. This type of extension creates a document given a filename. This is done by using the 'open' method within the class. Also, there is a 'prefs' function which will generate a GtkDialog. This dialog is then used to get any settings that the incoming file and extension may use. This function is executed, and the dialog returns, before the open method is called.</para>
+ <para>There are also several other settings stored in an Input extension. This includes information on the type of file the input module can take in including its filename extension and mime type. Also, there is a space to store a tooltip for additional information on the file type in the file dialog. Lastly, there is the key of which Output extension is recommended for saving this filetype. This is useful, as there is no other direct links between the Input and Output functions, and a user expects to be able to open and save without using the 'Save As...' dialog.</para>
</section>
<section>
<title>Output</title>
diff --git a/doc/nr-filter-interface.txt b/doc/nr-filter-interface.txt
index 6065333fe..6950317fc 100644
--- a/doc/nr-filter-interface.txt
+++ b/doc/nr-filter-interface.txt
@@ -19,7 +19,7 @@ Creates a new filter primitive under this filter object.
New primitive is placed so that it will be executed after all filter
primitives defined beforehand for this filter object.
Should this filter not have enough space for a new primitive, the filter
-is enlarged to accomodate the new filter element. It may be enlarged by more
+is enlarged to accommodate the new filter element. It may be enlarged by more
that one element.
Returns a pointer to the filter primitive created.
Returns NULL, if type is not valid filter primitive type or filter primitive
@@ -225,5 +225,5 @@ Passing either of these functions a negative value, NaN or infinity is
considered an error and no changes to filter state are made. If not set,
default value of zero is used, which means the filter results in
transparent black image.
-(NB: as for now, the default value can be overriden with configuration
+(NB: as for now, the default value can be overridden with configuration
file parameter options.filtertest)