Fixed typos.

Author: julianpistorius

.github/ISSUE_TEMPLATE/default_template.md

@@ -1,4 +1,4 @@
-*Fill out this issue by completing the items below. Not every item may be relevent to you, so feel free to make changes*
+*Fill out this issue by completing the items below. Not every item may be relevant to you, so feel free to make changes*
 
 #### The tutorial or vignette name
 Name:

index.Rmd

@@ -12,24 +12,24 @@ documentclass: book
 
 This book is intended to quickly introduce users to TERRA REF data through a series of tutorials. TERRA REF has many types of data, and most can be  accessed in multiple ways. Although this makes it more complicated to learn (and teach!), the objective is to provide users with the flexibility to access data in the most useful way.
 
-The first section walks the user through the steps of downloading and combining three different types of data: plot level phenotypes, meteorological data, and images. Subesquent sections provide more detailed examples that show how to access a larger variety of data and meta-data.
+The first section walks the user through the steps of downloading and combining three different types of data: plot level phenotypes, meteorological data, and images. Subsequent sections provide more detailed examples that show how to access a larger variety of data and meta-data.
 
 For those who are eager to see what is on deck, there are additional tutorials under development in the [tutorials repository](https://github.com/terraref/tutorials) on GitHub. These can be found in the traits, sensors, and genomics subfolders. Users are encouraged to revise and contribute new content.
 
 ## Pre-requisites
 
 While we assume that readers will have some familiarity with the nature of the problem - remote sensing of crop plants - for the most part, these tutorials assume that the user will bring their own scientific questions and a sense of curiosity and are eager to learn. 
 
-These tutorials are aimed at users who are familiar with or willing to learn programming languages including R (particularly for accessing plot level trait data) and Python (primarily for accessing environmental data and sensor data). In addition, there are examples of using SQL for more sophisticated database queries as well as the bash terminal.
+These tutorials are aimed at users who are familiar with or willing to learn programming languages including R (particularly for accessing plot level trait data) and Python (primarily for accessing environmental data and sensor data). In addition, there are examples of using SQL for more sophisticated database queries, as well as the Bash terminal.
 
-Some of the lessons only require a web browser; others will assume familarity with programming at the command line in (typically only one of) Python, R, and / or SQL. You should be willing to find help (see finding help, below).
+Some of the lessons only require a web browser; others will assume familiarity with programming at the command line in (typically only one of) Python, R, and / or SQL. You should be willing to find help (see finding help, below).
 
 ### Technical Requirements
 
 At a minimum, you should have:
 
 * An internet connection
-* Web Browser
+* Web browser
 * Access to the data that you are using
     + The tutorials will state which databases you will need access to
 * Software:
@@ -39,12 +39,12 @@ At a minimum, you should have:
 
 The first few chapters in the 'vignettes' section use publicly available sample data sets.
 Subsequent sections are also written to use publicly available data sets, but some of the examples require data that requires users to sign up.
-To sign up, you will need to 1) fill out the TERRA REF Beta user questionaire ([terraref.org/beta](https://terraref.org/beta)) and 2) request access to specific databases.
+To sign up, you will need to 1) fill out the TERRA REF Beta user questionnaire ([terraref.org/beta](https://terraref.org/beta)) and 2) request access to specific databases.
 
-<!-- Not sure where this goes, either in documentation or perhaps in an appendix. But I don't think this belongs in the introduction. Perhaps after the vignettes chaper 
+<!-- Not sure where this goes, either in documentation or perhaps in an appendix. But I don't think this belongs in the introduction. Perhaps after the vignettes chapter
 -->
 
-## Ways of Acessing Data
+## Ways of Accessing Data
 
 * Web Interfaces
     + [Clowder](https://docs.terraref.org/user-manual/how-to-access-data/using-clowder-sensor-and-genoomics-data) (sensor and genomic data)

metadata/metadata_tutorial_addition.Rmd

@@ -27,7 +27,7 @@ URL to a public published google sheet (you will need to provide this url in the
 
 # How to Run this Rmd
 
-Knitting this markdown file will not upload any data to the test database. Being able to knit this file means that you will not encounter any errors when uploading your metadata. All experiments, sites, treatments, cutlivars, and citations can be uploaded successfully. 
+Knitting this markdown file will not upload any data to the test database. Being able to knit this file means that you will not encounter any errors when uploading your metadata. All experiments, sites, treatments, cultivars, and citations can be uploaded successfully.
 
 To actually commit additions to the test database, you will need to make an edit to this markdown file. 
 

metadata/test_database_tutorial.Rmd

@@ -11,7 +11,7 @@ The purpose of this tutorial is to demonstrate how to set up a local instance of
 
 You will want to set up this test database when preparing to upload data to the master database.
 
-You should make sure that your data can be succesfully uploaded to the test database before trying to upload to master.
+You should make sure that your data can be successfully uploaded to the test database before trying to upload to master.
 
 # Requirements:
 
@@ -41,7 +41,7 @@ After initial set up, you will only need to run step 4 to restart the database.
 
 ## Step 1: Clone bety repository
 
-In a directory of your chioce, clone the bety repository from github and cd to the bety folder:
+In a directory of your choice, clone the bety repository from github and cd to the bety folder:
 
 ```sh
 git clone https://github.com/PecanProject/bety.git
@@ -107,7 +107,7 @@ Open a new tab in the terminal and connect to the test database using:
 ```sh
 psql -h localhost -p 5433 -U bety
 ```
-You should see the following prompt if you have succesfully logged into the test database:
+You should see the following prompt if you have successfully logged into the test database:
 ```sh
 psql (11.2, server 9.5.16)
 Type "help" for help.

sensors/01-meteorological-data.Rmd

@@ -147,7 +147,7 @@ The data represent 5 minute summaries aggregated from 1/s observations.
 ### Download data using the command line
 
 Data can be downloaded from Clowder using the command line program Curl. If the 
-following is typed into the commmand line, it will download the datapoints data 
+following is typed into the command line, it will download the datapoints data
 that we're interested in as a file which we have chosen to call `spectra.json`. 
 
 ```{sh eval=FALSE}

sensors/06-list-datasets-by-plot.Rmd

@@ -28,10 +28,10 @@ The *key* is a unique access key for the Clowder API.
 
 ## Getting the sensor list
 
-The first thing to get is the sensor name. This can be retreived using the
+The first thing to get is the sensor name. This can be retrieved using the
 `get_sensor_list` function. This function returns the full record which may
 be useful in some cases but primarily includes sensor names that include
-a plot id number. The utility function `unique_sensor_names` accpets the 
+a plot id number. The utility function `unique_sensor_names` accepts the
 sensor list and provides a list of names suitable for use in the 
 `get_file_listing` function.
 
@@ -96,7 +96,7 @@ of requests against the API it's possible to determine the files of interest and
 
 Each of the API URL's have the same beginning (https://terraref.ncsa.illinois.edu/clowder/api), 
 followed by the data needed for a specific request. As we step through the process you will be able
-to see how then end of the URL changes depending upon the reuqest.
+to see how then end of the URL changes depending upon the request.
 
 Below is what the API looks like as a URL. Try pasting it into your browser.
 
@@ -156,7 +156,7 @@ STREAM_ID=11586
 curl -o datasets.json -X GET "https://terraref.ncsa.illinois.edu/clowder/api/geostreams/datapoints?stream_id=${STREAM_ID}"
 ```
 
-After the call succeeds, a file named *datasets.json* is created containing the returned JSON onject. As part of the
+After the call succeeds, a file named *datasets.json* is created containing the returned JSON object. As part of the
 JSON object there are one or more `properties` fields containing *source_dataset* parameters.
 
 ```{javascript eval=FALSE}
@@ -211,7 +211,7 @@ of the files in the dataset with their IDs, and other data if available:
 
 ### Retrieving the files
 
-Given that a large number of files may be contained in a dataset, it may be desireable to automate the process of pulling down files
+Given that a large number of files may be contained in a dataset, it may be desirable to automate the process of pulling down files
 to the local system.
 
 For each file to be retrieved, the unique file ID is needed on the URL.

sensors/09-vnir-radiometer.Rmd

@@ -10,7 +10,7 @@ output: html_document
 
 An Ocean Optics STS Spectrometer measures downwelling solar spectral radiance every 5s on top of the Gantry.
 
-Lets look at the output from this sensor over the course of the day (and then we will see how to acces the data):
+Lets look at the output from this sensor over the course of the day (and then we will see how to access the data):
 
 ```{r one-downwelling-spectra}
 library(tidyverse)

traits/00-BETYdb-getting-started.Rmd

@@ -1,4 +1,4 @@
-# (PART\*) Secton 2: Traits {-}
+# (PART\*) Section 2: Traits {-}
 
 # Getting Started with BETYdb
 

traits/06-agronomic-metadata.Rmd

@@ -1,6 +1,6 @@
 # Querying Agronomic Meta-data
 
-In previous tutorials you have learned how to query trait data using a variety of different methods, including the web interface, an API, and the R traits package. Here you will continute to use the R traits package, and learn how to access meta-data from other tables in the database.
+In previous tutorials you have learned how to query trait data using a variety of different methods, including the web interface, an API, and the R traits package. Here you will continue to use the R traits package, and learn how to access meta-data from other tables in the database.
 
 While the basic search query that we have used in previous sections provides the key information that you may need for an analysis - the genotype name, the location, date, and method, there are other tables that contain more specific metadata.
 

traits/07-betydb-sql-access.Rmd

@@ -4,7 +4,7 @@ will be derived from https://github.com/pi4-uiuc/2017-bootcamp/blob/master/conte
 
 ## On workbench
 
-On the TERRA REF Workbench, you have access to the database. These connnections will only work if you are on the workbench.
+On the TERRA REF Workbench, you have access to the database. These connections will only work if you are on the workbench.
 
 
 ## Using PostgresSQL Studio