[Koha-docs] [PATCH] Fix typos found by codespell
Bernardo Gonzalez Kriegel
bgkriegel at gmail.com
Mon Nov 30 16:21:24 CET 2015
Hi Stefan,
could you generate a patch and send it to Nicole?
(git format-patch origin/master)
Regards,
Bernardo
--
Bernardo Gonzalez Kriegel
bgkriegel at gmail.com
On Thu, Nov 26, 2015 at 11:40 AM, Stefan Weil <sw at weilnetz.de> wrote:
> Am 02.11.2015 um 20:24 schrieb Stefan Weil:
> > Signed-off-by: Stefan Weil <sw at weilnetz.de>
> > ---
> > en/manual.xml | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/en/manual.xml b/en/manual.xml
> > index f1e2d4b..5e6e940 100644
> > --- a/en/manual.xml
> > +++ b/en/manual.xml
> > @@ -4704,7 +4704,7 @@ budget_code: 922$a</programlisting></para>
> > waiting for longer than the number of days specified in
> the
> > <link
> linkend="ReservesMaxPickUpDelay">ReservesMaxPickUpDelay</link>
> > system preference. Holds will only be cancelled if the
> <link linkend="expiredholdscron">Expire Holds cron job</link> is
> > - runnning.</para>
> > + running.</para>
> > </listitem>
> > </itemizedlist>
> > </section>
> > @@ -5767,7 +5767,7 @@ budget_code: 922$a</programlisting></para>
> > <para>Koha can track the number of times and item is
> checked
> > out and store that on the item record in the database.
> This
> > information is not stored by default. Setting this
> preference
> > - to 'Do' will tell Koha to track that info everytime the
> item
> > + to 'Do' will tell Koha to track that info every time
> the item
> > is checked out in real time. Otherwise you could use
> the <link linkend="updateissuescron">cron job</link> to have Koha update
> > that field nightly.</para>
> > </listitem>
> > @@ -23244,7 +23244,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > <para>Click 'Add action'</para>
> > </listitem>
> > </itemizedlist></para>
> > - <para>Each action can also have an optional condition to check
> the value or existance of
> > + <para>Each action can also have an optional condition to check
> the value or existence of
> > another field. For example you might want to add the call
> number to the item record if
> > it's not already there.</para>
> > <screenshot>
> > @@ -23260,7 +23260,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > <para>Choose 'Copy'</para>
> > </listitem>
> > <listitem>
> > - <para>Decide if you want to copy the first occurance or all
> occurances of the
> > + <para>Decide if you want to copy the first occurrence or
> all occurrences of the
> > field</para>
> > </listitem>
> > <listitem>
> > @@ -23302,7 +23302,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > <para>Choose 'Copy and replace'</para>
> > </listitem>
> > <listitem>
> > - <para>Decide if you want to copy the first occurance or all
> occurances of the
> > + <para>Decide if you want to copy the first occurrence or
> all occurrences of the
> > field</para>
> > </listitem>
> > <listitem>
> > @@ -23354,7 +23354,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > <para>Choose 'Copy and replace'</para>
> > </listitem>
> > <listitem>
> > - <para>Decide if you want to copy the first occurance or
> all occurances of the
> > + <para>Decide if you want to copy the first occurrence or
> all occurrences of the
> > field</para>
> > </listitem>
> > <listitem>
> > @@ -23488,7 +23488,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > <para>Choose the character encoding</para>
> >
> > <screenshot>
> > - <screeninfo>Chracter encoding</screeninfo>
> > + <screeninfo>Character encoding</screeninfo>
> >
> > <mediaobject>
> > <imageobject>
> > @@ -31539,7 +31539,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > item. Learn more about Analytics in Chapter 13 of AACR2.</para>
> >
> > <para>If you would like to catalog analytic records there are
> two options. One is to use the
> > - <link linkend="catalogeasyanalytics">Easy Analytics</link>
> funtion; the other is the
> > + <link linkend="catalogeasyanalytics">Easy Analytics</link>
> function; the other is the
> > <link linkend="catalogenhanceanalytics">Analytics Enhanced
> Workflow</link>.</para>
> > <section id="catalogeasyanalytics">
> > <title>Easy Analytics</title>
> > @@ -34309,7 +34309,7 @@ location: [STAFF, ISO]</programlisting>Will
> block items with an itype code of
> > </section>
> > <section id="serialpatterns">
> > <title>Manage Serial Numbering Patterns</title>
> > - <para>Everytime you create a new numbering pattern in serials you
> can save it for later use.
> > + <para>Every time you create a new numbering pattern in serials
> you can save it for later use.
> > These patters are accessible via the Manage numbering patterns
> page.</para>
> > <itemizedlist>
> > <listitem>
> > @@ -46926,7 +46926,7 @@
> http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd
> > make the cover image fetcher configurable so we can use any data
> source for cover image
> > fetching.</para>
> > <para>Second, we need to configure the plugin. The plugin
> configuration is a single text area
> > - that uses YAML ( actually, it’s JSON, whcih is a subset of YAML )
> to store the configuration
> > + that uses YAML ( actually, it’s JSON, which is a subset of YAML )
> to store the configuration
> > options. In this example it looks like
> > this:<programlisting>- id: 42
> > selector: #coverflow
>
> Ping. Will this patch for koha-docs be applied?
>
> Stefan
>
> _______________________________________________
> Koha-docs mailing list
> Koha-docs at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.koha-community.org/cgi-bin/mailman/private/koha-docs/attachments/20151130/1c166b52/attachment.html>
More information about the Koha-docs
mailing list