Git commit e3564ef6ae5873948df2bc39c66c004e4f393b97 by Yuri Chornoivan.
Committed on 19/01/2017 at 20:08.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +3    -3    doc/rkwardplugins/index.docbook

https://commits.kde.org/rkward/e3564ef6ae5873948df2bc39c66c004e4f393b97

diff --git a/doc/rkwardplugins/index.docbook b/doc/rkwardplugins/index.docbook
index aa091b28..8251a23c 100644
--- a/doc/rkwardplugins/index.docbook
+++ b/doc/rkwardplugins/index.docbook
@@ -1979,7 +1979,7 @@ x </components ...>
        <para>
                So far we have used a few concepts regarding translations or 
"i18n" (short for "internationalization", which has 18 characters between i and 
n) in passing. In this chapter we
                give a more in-depth account of what i18n functionally for 
&rkward; plugins. For the most part you will <emphasis>not</emphasis> need all 
of this in your plugins. However,
-               it may be a good idea to read over this chapter in full, as 
understanding these concept should help you creating plugins that are fully 
translatable, and that allow for a high
+               it may be a good idea to read over this chapter in full, as 
understanding these concepts should help you creating plugins that are fully 
translatable, and that allow for a high
                quality of translations.
        </para>
        <sect1 id="i18n_general"><title>General considerations</title>
@@ -2586,7 +2586,7 @@ plugin.dir &lt;- rk.plugin.skeleton("t-Test",
        edit=TRUE,
        show=TRUE)
                        </programlisting>
-                       <para>The files will be created in a temporal directory 
by default. The last three options are not necessary, but very handy: 
<parameter>load=</parameter><replaceable>TRUE</replaceable> will automatically 
add the new plugin to &rkward;s configuration (since it's in a temp dir and 
hence will cease to exist when &rkward; is closed, it will automatically be 
removed again by &rkward; during its next start), 
<parameter>edit=</parameter><replaceable>TRUE</replaceable> will open all 
created files for editing in &rkward; editor tabs, and 
<parameter>show=</parameter><replaceable>TRUE</replaceable> will attempt to 
directly launch the plugin, so you can examine what it looks like without a 
klick. You might consider adding 
<parameter>overwrite=</parameter><replaceable>TRUE</replaceable> if you're 
about to run your script repeatedly (&eg; after changes to the code), as by 
default no files will be overwritten.</para>
+                       <para>The files will be created in a temporal directory 
by default. The last three options are not necessary, but very handy: 
<parameter>load=</parameter><replaceable>TRUE</replaceable> will automatically 
add the new plugin to &rkward;s configuration (since it's in a temp dir and 
hence will cease to exist when &rkward; is closed, it will automatically be 
removed again by &rkward; during its next start), 
<parameter>edit=</parameter><replaceable>TRUE</replaceable> will open all 
created files for editing in &rkward; editor tabs, and 
<parameter>show=</parameter><replaceable>TRUE</replaceable> will attempt to 
directly launch the plugin, so you can examine what it looks like without a 
click. You might consider adding 
<parameter>overwrite=</parameter><replaceable>TRUE</replaceable> if you're 
about to run your script repeatedly (&eg; after changes to the code), as by 
default no files will be overwritten.</para>
                        <para>The result object <quote>plugin.dir</quote> 
contains the path to the directory in which the plugin was created. This can be 
useful in combination with the function 
<function>rk.build.package()</function>, to build an actual &r; package to 
share your plugin with others -- &eg; by sending it to the &rkward; development 
team to be added to our plugin repository.</para>
                </sect2>
                <sect2 id="rkdev_ttest_script"><title>The full script</title>
@@ -3116,7 +3116,7 @@ new Header(i18n("Test results")).print();
        </varlistentry>
        <varlistentry>
        <term><parameter>types</parameter></term>
-       <listitem><para>If you specify one or more variables types (separated 
by spaced (" ")), here, the varslot will only accept objects of those types. 
Valid types are "unknown", "number", "string", "factor", "invalid". (Optional, 
<emphasis>use with great care</emphasis>, the user should not be prevented from 
making valid choices, and rkward does not always know the type of a 
variable)</para></listitem>
+       <listitem><para>If you specify one or more variables types (separated 
by spaces (" ")), here, the varslot will only accept objects of those types. 
Valid types are "unknown", "number", "string", "factor", "invalid". (Optional, 
<emphasis>use with great care</emphasis>, the user should not be prevented from 
making valid choices, and &rkward; does not always know the type of a 
variable)</para></listitem>
        </varlistentry>
        <varlistentry>
        <term><parameter>num_dimensions</parameter></term>

Reply via email to