Merge pull request #12 from justbennet/copyedit

Copyediting only.

Author: chrisgorgo

README.md

@@ -3,40 +3,40 @@ Every BIDS App needs to follow a minimal set of command arguments common across
 all of the Apps. This allows users and developers to easily use and integrate
 BIDS Apps with their environment.
 
-This is an minimalistic example BIDS App consisting of a Dockerfile and simple
-entrypoint script (written in this case in Python) accepting the standard BIDS
+This is a minimalist example of a BIDS App consisting of a Dockerfile and a simple
+entry point script (written in this case in Python) accepting the standard BIDS
 Apps command line arguments. This repository can be used as a template for new BIDS Apps.
 
 For more information about the specification of BIDS Apps see [here](https://docs.google.com/document/d/1E1Wi5ONvOVVnGhj21S1bmJJ4kyHFT7tkxnV3C23sjIE/edit#).
 
 ### Description
-This is a placeholder for a shaort description explaining the user what your App is doing.
+This is a placeholder for a short description explaining to the user what your App will doing.
 
 ### Documentation
-Provide a link to a documention of your pipeline.
+Provide a link to the documention of your pipeline.
 
 ### How to report errors
-Provide instruction for users on how to get help and report errors.
+Provide instructions for users on how to get help and report errors.
 
 ### Acknowledgements
-Describe how would you like users to acknoledge the use of your App in their papers (citation, a paragraph that should be copy pasted etc.)
+Describe how would you would like users to acknowledge use of your App in their papers (citation, a paragraph that can be copy pasted, etc.)
 
 ### Usage
-This App has the following comman line arguments:
+This App has the following command line arguments:
 
 		usage: run.py [-h]
 		              [--participant_label PARTICIPANT_LABEL [PARTICIPANT_LABEL ...]]
 		              bids_dir output_dir {participant,group}
 
-		Example BIDS App entrypoint script.
+		Example BIDS App entry point script.
 
 		positional arguments:
 		  bids_dir              The directory with the input dataset formatted
 		                        according to the BIDS standard.
 		  output_dir            The directory where the output files should be stored.
-		                        If you are running group level analysis this folder
+		                        If you are running a group level analysis, this folder
 		                        should be prepopulated with the results of
-		                        theparticipant level analysis.
+		                        the participant level analysis.
 		  {participant,group}   Level of the analysis that will be performed. Multiple
 		                        participant level analyses can be run independently
 		                        (in parallel).
@@ -48,7 +48,7 @@ This App has the following comman line arguments:
 		                        analyzed. The label corresponds to
 		                        sub-<participant_label> from the BIDS spec (so it does
 		                        not include "sub-"). If this parameter is not provided
-		                        all subjects should be analyzed. Multiple participants
+		                        all subjects will be analyzed. Multiple participants
 		                        can be specified with a space separated list.
 
 To run it in participant level mode (for one participant):
@@ -59,7 +59,7 @@ To run it in participant level mode (for one participant):
 		bids/example \
 		/bids_dataset /outputs participant --participant_label 01
 
-After doing this for all subjects (potentially in parallel) the group level analysis
+After doing this for all subjects (potentially in parallel), the group level analysis
 can be run:
 
     docker run -i --rm \
@@ -69,7 +69,7 @@ can be run:
 		/bids_dataset /outputs group
 
 ### Special considerations
-Describe if your app has some special requirements. For example:
+Describe whether your app has any special requirements. For example:
 
 - Multiple map reduce steps (participant, group, participant2, group2 etc.)
 - Unusual memory requirements