From 4e1897e074e7197fe933ee25cebc5253ef870980 Mon Sep 17 00:00:00 2001
From: Ed Hartnett <edwardjameshartnett@gmail.com>
Date: Tue, 30 Apr 2019 09:26:07 -0600
Subject: [PATCH] fixed docs

---
 doc/source/GettingStarted.txt | 40 +++++++++++++++++++++++++++++------
 1 file changed, 34 insertions(+), 6 deletions(-)

diff --git a/doc/source/GettingStarted.txt b/doc/source/GettingStarted.txt
index 40fe348d534..d2aaaf3603e 100644
--- a/doc/source/GettingStarted.txt
+++ b/doc/source/GettingStarted.txt
@@ -20,21 +20,49 @@
 
 /*! \page intro Introduction 
 
-PIO is a software interface layer designed to encapsolate the complexities of parallel IO and make it easier to replace the lower level software backend.  It currently supports <a href=http://www.unidata.ucar.edu/software/netcdf/docs/html_guide/index.html#user_guide> netcdf </a>  and <a href=http://trac.mcs.anl.gov/projects/parallel-netcdf> pnetcdf </a>.
+PIO is a software interface layer designed to encapsolate the
+complexities of parallel IO and make it easier to replace the lower
+level software backend.  It currently supports <a
+href=http://www.unidata.ucar.edu/software/netcdf/docs/html_guide/index.html#user_guide>
+netcdf </a> and <a
+href=http://trac.mcs.anl.gov/projects/parallel-netcdf> pnetcdf </a>.
 
 Basic description of how to optimize IO in a parallel environment...
 
-PIO calls are collective.  A MPI communicator is set in a call to \ref PIO_init and all tasks associated with that communicator must participate in all subsequent calls to PIO.  An application can make multiple calls to \ref PIO_init in order to support multiple MPI communicators.
+PIO calls are collective.  A MPI communicator is set in a call to \ref
+PIO_init and all tasks associated with that communicator must
+participate in all subsequent calls to PIO.  An application can make
+multiple calls to \ref PIO_init in order to support multiple MPI
+communicators.
 
-Begin by checking out a copy from [gitHub](https://github.com/PARALLELIO/ParallelIO) and installing on your system as per the instructions in the [Installation](@ref install) document. Take a look at examples of PIO usage in both complex and simple test programs in the [Examples](@ref examp) document. Finally, read through the [FAQ](@ref faq) to see if any remaining questions can be answered. 
+Begin by getting and unpacking the most recent release of PIO from
+[gitHub](https://github.com/PARALLELIO/ParallelIO/releases) and
+installing on your system as per the instructions in the
+[Installation](@ref install) document. Take a look at examples of PIO
+usage in both complex and simple test programs in the [Examples](@ref
+examp) document. Finally, read through the [FAQ](@ref faq) to see if
+any remaining questions can be answered.
 
 ### Using PIO has three basic steps. ###
 
-1. Your program should call the \ref PIO_init function, and provide the MPI communicator (and the rank within that communicator) of the calling task. This call initializes an IO system type structure that will be used in subsequent file and decomposition functions.
+1. Your program should call the \ref PIO_init function, and provide
+the MPI communicator (and the rank within that communicator) of the
+calling task. This call initializes an IO system type structure that
+will be used in subsequent file and decomposition functions.
 
-2. You can open a file for reading or writing with a call to \ref PIO_createfile or \ref PIO_openfile. In this call you will specify the file type: pio_iotype_netcdf, pio_iotype_pnetcdf, pio_iotype_netcdf4c or pio_iotype_netcdf4p; along with the file name and optionally the netcdf mode.
+2. You can open a file for reading or writing with a call to \ref
+PIO_createfile or \ref PIO_openfile. In this call you will specify the
+file type: pio_iotype_netcdf, pio_iotype_pnetcdf, pio_iotype_netcdf4c
+or pio_iotype_netcdf4p; along with the file name and optionally the
+netcdf mode.
 
-3. Finally, you can read or write decomposed data to the output file. You must describe the mapping between the organization of data in the file and that same data in the application space.  This is done in a call to \ref PIO_initdecomp. In the simplest call to this function, a one dimensional integer array is passed from each task, the values in the array represent the offset from the beginning of the array on file. (what happens next?)
+3. Finally, you can read or write decomposed data to the output
+file. You must describe the mapping between the organization of data
+in the file and that same data in the application space.  This is done
+in a call to \ref PIO_initdecomp. In the simplest call to this
+function, a one dimensional integer array is passed from each task,
+the values in the array represent the offset from the beginning of the
+array on file.
 
 
 */