Minor wording tweak

README.Rmd

@@ -107,7 +107,7 @@ prepareDatabase('accessionTaxa.sql')
 
 If everything works then that should have prepared a SQLite database ready for use. You can skip the "Manual preparation" steps below.
 
-All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and call the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
+All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and recall the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
 
 ```{r,eval=FALSE}
 prepareDatabase('accessionTaxa.sql')

README.md

@@ -112,7 +112,7 @@ prepareDatabase('accessionTaxa.sql')
 
 If everything works then that should have prepared a SQLite database ready for use. You can skip the "Manual preparation" steps below.
 
-All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and call the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
+All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and recall the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
 
 
 ```r

inst/doc/usage.Rmd

@@ -112,7 +112,7 @@ prepareDatabase('accessionTaxa.sql')
 
 If everything works then that should have prepared a SQLite database ready for use. You can skip the "Manual preparation" steps below.
 
-All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and call the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
+All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and recall the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
 
 ```{r,eval=FALSE}
 prepareDatabase('accessionTaxa.sql')

inst/doc/usage.html

@@ -116,7 +116,7 @@ <h2>Preparation<a name="preparation"></a></h2>
 <pre><code>## Adding index. This may also take a while.</code></pre>
 <pre><code>## [1] &quot;accessionTaxa.sql&quot;</code></pre>
 <p>If everything works then that should have prepared a SQLite database ready for use. You can skip the “Manual preparation” steps below.</p>
-<p>All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and call the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:</p>
+<p>All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and recall the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:</p>
 <div class="sourceCode"><pre class="sourceCode r"><code class="sourceCode r"><span class="kw">prepareDatabase</span>(<span class="st">'accessionTaxa.sql'</span>)</code></pre></div>
 <pre><code>## SQLite database accessionTaxa.sql already exists. Delete to regenerate</code></pre>
 <pre><code>## [1] &quot;accessionTaxa.sql&quot;</code></pre>

vignettes/usage.Rmd

@@ -112,7 +112,7 @@ prepareDatabase('accessionTaxa.sql')
 
 If everything works then that should have prepared a SQLite database ready for use. You can skip the "Manual preparation" steps below.
 
-All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and call the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
+All files are cached locally and so the preparation is only required once (delete/rename the SQLite database and recall the function to regenerate the database). It is not necessary to manually check for the presence of the database since the function checks to see if SQLite database is present and if so skips downloading/processing. For example, running the command again produces:
 
 ```{r,eval=FALSE}
 prepareDatabase('accessionTaxa.sql')