summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorluz.paz <luzpaz@users.noreply.github.com>2018-06-30 12:56:14 +0000
committerluz paz <luzpaz@users.noreply.github.com>2018-09-11 19:26:04 +0000
commitd598a3a5662a0ce6d60b39d272fce9a278b348aa (patch)
tree01411005c8d350718316c095d2c19e3b0b49e35b /doc
parentRefactor xml editor, improve UI and prepare for future additions (diff)
downloadinkscape-d598a3a5662a0ce6d60b39d272fce9a278b348aa.tar.gz
inkscape-d598a3a5662a0ce6d60b39d272fce9a278b348aa.zip
Misc. typos
Found via `codespell -q 3 -I ../inkscape-whitelist.txt --skip="*.svg,*.po,*.nsh,*.in,./src/3rdparty"`
Diffstat (limited to 'doc')
-rw-r--r--doc/extension_system.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/extension_system.xml b/doc/extension_system.xml
index dc6d25ecc..fee50e904 100644
--- a/doc/extension_system.xml
+++ b/doc/extension_system.xml
@@ -186,7 +186,7 @@
<para>Internal Extensions are in a way the reverse of a normal Extension, in that instead of providing a way to hook into Inkscape from the outside, they provide hooks from inside Inkscape. These are used directly by Inkscape, such as in the case of compiled-in printing modules. Most users will never need to write this type of extension, they are pretty much for Inkscape core developers only.</para>
</section>
<section>
- <title>Writeing Your Extension</title>
+ <title>Writing Your Extension</title>
<para>This section provides some guidance and examples for implementing different kinds of Extensions.</para>
<section>
<title>Writing Script Extensions</title>