Small cleanup with mdl and markdownlint-cli

 In general I agree that bare URLs are bad and some lines in the links
 section are too long, but this is a good improvement, and low hanging
 fruit.

Author: zbeekman

README.md

@@ -19,7 +19,6 @@ OpenCoarrays
 [![Download as PDF][pdf img]](https://md2pdf.herokuapp.com/sourceryinstitute/OpenCoarrays/blob/master/README.pdf)
 [![Twitter URL][twitter img]][default tweet]
 
-
 [Overview](#overview) ·
 [Downloads](#downloads) ·
 [Compatibility](#compatibility) ·
@@ -36,13 +35,42 @@ OpenCoarrays
 
 Overview
 --------
-[OpenCoarrays] is an open-source software project that supports the coarray Fortran (CAF) parallel programming features of the Fortran 2008 standard and several features proposed for Fortran 2015 in the draft Technical Specification [TS 18508] _Additional Parallel Features in Fortran_.
-
-OpenCoarrays provides a compiler wrapper (named `caf`), a runtime library (named `libcaf_mpi.a` by default), and an executable file launcher (named `cafrun`).  With OpenCoarrays-aware compilers, the compiler wrapper passes the provided source code to the chosen compiler (`mpif90` by default).  For non-OpenCoarrays-aware compilers, the wrapper transforms CAF syntax into OpenCoarrays procedure calls before invoking the chosen compiler on the transformed code.  The runtime library supports compiler communication and synchronization requests by invoking a lower-level communication library--the Message Passing Interface ([MPI]) by default.  The launcher passes execution to the chosen communication library's parallel program launcher (`mpirun` by default).
 
-OpenCoarrays defines an application binary interface ([ABI]) that translates high-level communication and synchronization requests into low-level calls to a user-specified communication library.  This design decision liberates compiler teams from hardwiring communication-library choice into their compilers and it frees Fortran programmers to express parallel algorithms once and reuse identical CAF source with whichever communication library is most efficient for a given hardware platform.  The communication substrate for OpenCoarrays built with the preferred build system, CMake, is the Message Passing Interface ([MPI]).
-
-OpenCoarrays enables CAF application developers to express parallel algorithms without hardwiring a particular version of a particular communication library or library version into their codes.  Such abstraction makes application code less sensitive to the evolution of the underlying communication libraries and hardware platforms.
+[OpenCoarrays] is an open-source software project
+that supports the coarray Fortran (CAF) parallel programming features
+of the Fortran 2008 standard and several features proposed for Fortran
+2015 in the draft Technical Specification [TS 18508] _Additional
+Parallel Features in Fortran_.
+
+OpenCoarrays provides a compiler wrapper (named `caf`), a runtime
+library (named `libcaf_mpi.a` by default), and an executable file
+launcher (named `cafrun`).  With OpenCoarrays-aware compilers, the
+compiler wrapper passes the provided source code to the chosen
+compiler (`mpif90` by default).  For non-OpenCoarrays-aware compilers,
+the wrapper transforms CAF syntax into OpenCoarrays procedure calls
+before invoking the chosen compiler on the transformed code.  The
+runtime library supports compiler communication and synchronization
+requests by invoking a lower-level communication library--the Message
+Passing Interface ([MPI]) by default.  The launcher passes execution
+to the chosen communication library's parallel program launcher
+(`mpirun` by default).
+
+OpenCoarrays defines an application binary interface ([ABI]) that
+translates high-level communication and synchronization requests into
+low-level calls to a user-specified communication library.  This
+design decision liberates compiler teams from hardwiring
+communication-library choice into their compilers and it frees Fortran
+programmers to express parallel algorithms once and reuse identical
+CAF source with whichever communication library is most efficient for
+a given hardware platform.  The communication substrate for
+OpenCoarrays built with the preferred build system, CMake, is the
+Message Passing Interface ([MPI]).
+
+OpenCoarrays enables CAF application developers to express parallel
+algorithms without hardwiring a particular version of a particular
+communication library or library version into their codes.  Such
+abstraction makes application code less sensitive to the evolution of
+the underlying communication libraries and hardware platforms.
 
 Downloads
 ---------
@@ -51,13 +79,34 @@ Please see our [Releases] page.
 
 Compatibility
 -------------
-The GNU Compiler Collection ([GCC]) Fortran front end ([gfortran]) is OpenCoarrays-aware for release versions 5.1.0 and higher.  Users of other compilers, including earlier versions of gfortran, can access a limited subset of CAF features via the provided [opencoarrays module].  After installation, please execute the `caf` script (which is installed in the `bin` directory of the installation path) with no arguments to see a list of the corresponding limitations.  Please also notify the corresponding compiler vendor and the OpenCoarrays team that you would like for a future version of the compiler to be OpenCoarrays-aware.
+
+The GNU Compiler Collection ([GCC]) Fortran front end ([gfortran]) is
+OpenCoarrays-aware for release versions 5.1.0 and higher.  Users of
+other compilers, including earlier versions of gfortran, can access a
+limited subset of CAF features via the provided [opencoarrays module].
+After installation, please execute the `caf` script (which is
+installed in the `bin` directory of the installation path) with no
+arguments to see a list of the corresponding limitations.  Please also
+notify the corresponding compiler vendor and the OpenCoarrays team
+that you would like for a future version of the compiler to be
+OpenCoarrays-aware.
 
 Prerequisites
 -------------
-We expect our LIBCAF_MPI library to be the default OpenCoarrays library.  LIBCAF_MPI is the most straightforward to install and use, the most robust in terms of its internal complexity, and the most frequently updated and maintained.  Building LIBCAF_MPI requires prior installation of an MPI implementation.  We recommend [MPICH] generally or, if available, [MVAPICH] for better performance. [OpenMPI] is another option.
 
-We offer an unsupported LIBCAF_GASNet alternative.  We intend for LIBCAF_GASNet to be an "expert" alternative capable of outperforming MPI for some applications on some platforms.  LIBCAF_GASNet requires greater care to configure and use and building LIBCAF_GASNet requires prior installation of [GASNet].
+We expect our LIBCAF_MPI library to be the default OpenCoarrays
+library.  LIBCAF_MPI is the most straightforward to install and use,
+the most robust in terms of its internal complexity, and the most
+frequently updated and maintained.  Building LIBCAF_MPI requires prior
+installation of an MPI implementation.  We recommend [MPICH] generally
+or, if available, [MVAPICH] for better performance. [OpenMPI] is
+another option.
+
+We offer an unsupported LIBCAF_GASNet alternative.  We intend for
+LIBCAF_GASNet to be an "expert" alternative capable of outperforming
+MPI for some applications on some platforms.  LIBCAF_GASNet requires
+greater care to configure and use and building LIBCAF_GASNet requires
+prior installation of [GASNet].
 
 Installation
 ------------
@@ -84,20 +133,33 @@ Support
 -------
 
 * Please submit bug reports and feature requests via our [Issues] page.
-* Please submit questions regarding installation and use via our [Google Group] by signing into [Google Groups] or [subscribing] and sending email to [[email protected]].
+* Please submit questions regarding installation and use via our
+  [Google Group] by signing into [Google Groups] or [subscribing] and
+  sending email to [[email protected]].
 
 Acknowledgements
 ----------------
+
 We gratefully acknowledge support from the following institutions:
 
-* [National Center for Atmospheric Research] for access to the Yellowstone/Caldera supercomputers and for logistics support during the initial development of OpenCoarrays.
-* [CINECA] for access to Eurora/PLX for the project HyPS- BLAS under the ISCRA grant program for 2014.
-* [Google] for support of a related [Google Summer of Code] 2014 project.
-* The National Energy Research Scientific Computing Center ([NERSC]), which is supported by the Office of Science of the U.S. Department of Energy under Contract No. DE-AC02-05CH11231, for access to the Hopper and Edison supercomputers under the OpenCoarrays project start allocation.
-* [Sourcery, Inc.], for financial support for the domain registration, web hosting, advanced development, and conference travel.
+* [National Center for Atmospheric Research] for access to the
+  Yellowstone/Caldera supercomputers and for logistics support during
+  the initial development of OpenCoarrays.
+* [CINECA] for access to Eurora/PLX for the project HyPS- BLAS under
+  the ISCRA grant program for 2014.
+* [Google] for support of a related [Google Summer of Code] 2014
+  project.
+* The National Energy Research Scientific Computing Center ([NERSC]),
+  which is supported by the Office of Science of the U.S. Department
+  of Energy under Contract No. DE-AC02-05CH11231, for access to the
+  Hopper and Edison supercomputers under the OpenCoarrays project
+  start allocation.
+* [Sourcery, Inc.], for financial support for the domain registration,
+  web hosting, advanced development, and conference travel.
 
 Donate
 ------
+
 If you find this software useful, please consider donating
 [your time](CONTRIBUTING.md) or
 [your money](http://www.sourceryinstitute.org/store/p5/Donation.html)
@@ -150,7 +212,6 @@ to aid in development efforts.
 [[email protected]]: mailto:[email protected]
 [Google Summer of Code]: https://www.google-melange.com/archive/gsoc/2014/orgs/gcc
 
-
 [Issues]: https://github.com/sourceryinstitute/OpenCoarrays/issues
 [Releases]: https://github.com/sourceryinstitute/OpenCoarrays/releases