lesson 3 typos

Author: mikblack

R_Packages_Functions/03_package_anatomy.Rmd

@@ -14,19 +14,19 @@ output: ioslides_presentation
     - pdf: http://shop.oreilly.com/product/0636920034421.do
     - paper/kindle: http://www.amazon.com/dp/1491910593/
  - There are a few more things worth knowing though... (and many of them I learned from Hadley)
- - Note that Hadley's approach to creating packages is based on some additional functionality provided by RStudio: we haven't explicity utilized that here (more later).
+ - Note that Hadley's approach to creating packages is based on some additional functionality provided by RStudio: we haven't explicitly utilized that here (more later).
 
 ## Aside - it's a package, not a library...
 
- - Just a minor pont:
+ - Just a minor point:
     - package: the thing we just made (basically a collection of functions).
-    - library: a place where lots of packages live (i.e., a directory in your computer's filesystem).
+    - library: a place where lots of packages live (i.e., a directory in your computer's file system).
 
 ## What is in our package?
  - Code: the 'R' directory
  - Package metadata: DESCRIPTION file
     - developer info (that's you)
-    - includes dependency infomation (packages, R version etc)
+    - includes dependency information (packages, R version etc)
     - version number
  - Documentation: the man directory
     - Objects and functions
@@ -63,7 +63,7 @@ list.files(pattern="*.gz")
 
 ## Sharing your package
 
- - Easy to share aa version you package with others.
+ - Easy to share a version of your package with others.
  - What happens when you change something?
  - Need a system that allows users to automatically update their version of the package, without you having to rebuild it and send it to them.
  - Perhaps time for some version control....
@@ -72,7 +72,7 @@ list.files(pattern="*.gz")
 
  - Git provides the ability to track changes to the files that make up your package.
  - GitHub extends this functionality be providing a centralised repository where the evolving (and stable) versions of a package can be stored, and accessed by others.
- - The `devtools` packages provides an interface between R and GitHub, so that packages can be installed directly from a github repository.
+ - The `devtools` packages provides an interface between R and GitHub, so that packages can be installed directly from a GitHub repository.
  - We've already done this with the `roxygen2` package: 
 ```{r, eval=F}
 devtools::install_github("klutometis/roxygen")
@@ -81,11 +81,11 @@ devtools::install_github("klutometis/roxygen")
 
 ## The beauty of devtools...    
 
- - `devtools` has made package dvelopment and distribution simple
+ - `devtools` has made package development and distribution simple
      - Previously developers had to release packages through an established repository (e.g., CRAN or Bioconductor), or host copies of the package source code that could be downloaded and installed.
      - Now the same tools being used to provide centralised version control (Git and GitHub), are also being used for package distribution.     
  - Even if you're only developing packages for yourself, the combination of `devtools`, `roxygen2`, Git and GitHub is a powerful development platform.
- - Now you just need to impliment some testing...
+ - Now you just need to implement some testing...
 
 
 

R_Packages_Functions/03_package_anatomy.html

@@ -105,17 +105,17 @@ <h2 data-config-subtitle><!-- populated from slide_config.json --></h2>
 <li>paper/kindle: <a href='http://www.amazon.com/dp/1491910593/' title=''>http://www.amazon.com/dp/1491910593/</a></li>
 </ul></li>
 <li>There are a few more things worth knowing though&#8230; (and many of them I learned from Hadley)</li>
-<li>Note that Hadley&#39;s approach to creating packages is based on some additional functionality provided by RStudio: we haven&#39;t explicity utilized that here (more later).</li>
+<li>Note that Hadley&#39;s approach to creating packages is based on some additional functionality provided by RStudio: we haven&#39;t explicitly utilized that here (more later).</li>
 </ul>
 
 </article></slide><slide class=''><hgroup><h2>Aside - it&#39;s a package, not a library&#8230;</h2></hgroup><article  id="aside---its-a-package-not-a-library...">
 
 <ul>
-<li>Just a minor pont:
+<li>Just a minor point:
 
 <ul>
 <li>package: the thing we just made (basically a collection of functions).</li>
-<li>library: a place where lots of packages live (i.e., a directory in your computer&#39;s filesystem).</li>
+<li>library: a place where lots of packages live (i.e., a directory in your computer&#39;s file system).</li>
 </ul></li>
 </ul>
 
@@ -127,7 +127,7 @@ <h2 data-config-subtitle><!-- populated from slide_config.json --></h2>
 
 <ul>
 <li>developer info (that&#39;s you)</li>
-<li>includes dependency infomation (packages, R version etc)</li>
+<li>includes dependency information (packages, R version etc)</li>
 <li>version number</li>
 </ul></li>
 <li>Documentation: the man directory
@@ -187,7 +187,7 @@ <h2 data-config-subtitle><!-- populated from slide_config.json --></h2>
 </article></slide><slide class=''><hgroup><h2>Sharing your package</h2></hgroup><article  id="sharing-your-package">
 
 <ul>
-<li>Easy to share aa version you package with others.</li>
+<li>Easy to share a version of your package with others.</li>
 <li>What happens when you change something?</li>
 <li>Need a system that allows users to automatically update their version of the package, without you having to rebuild it and send it to them.</li>
 <li>Perhaps time for some version control&#8230;.</li>
@@ -198,7 +198,7 @@ <h2 data-config-subtitle><!-- populated from slide_config.json --></h2>
 <ul>
 <li>Git provides the ability to track changes to the files that make up your package.</li>
 <li>GitHub extends this functionality be providing a centralised repository where the evolving (and stable) versions of a package can be stored, and accessed by others.</li>
-<li>The <code>devtools</code> packages provides an interface between R and GitHub, so that packages can be installed directly from a github repository.</li>
+<li>The <code>devtools</code> packages provides an interface between R and GitHub, so that packages can be installed directly from a GitHub repository.</li>
 <li>We&#39;ve already done this with the <code>roxygen2</code> package:</li>
 </ul>
 
@@ -211,14 +211,14 @@ <h2 data-config-subtitle><!-- populated from slide_config.json --></h2>
 </article></slide><slide class=''><hgroup><h2>The beauty of devtools&#8230;</h2></hgroup><article  id="the-beauty-of-devtools...">
 
 <ul>
-<li><code>devtools</code> has made package dvelopment and distribution simple
+<li><code>devtools</code> has made package development and distribution simple
 
 <ul>
 <li>Previously developers had to release packages through an established repository (e.g., CRAN or Bioconductor), or host copies of the package source code that could be downloaded and installed.</li>
 <li>Now the same tools being used to provide centralised version control (Git and GitHub), are also being used for package distribution.<br/></li>
 </ul></li>
 <li>Even if you&#39;re only developing packages for yourself, the combination of <code>devtools</code>, <code>roxygen2</code>, Git and GitHub is a powerful development platform.</li>
-<li>Now you just need to impliment some testing&#8230;</li>
+<li>Now you just need to implement some testing&#8230;</li>
 </ul></article></slide>