Readme (#19)

* changing looks of readme

* reordering

* added links to pep8

Author: babbush

README.rst

@@ -40,30 +40,11 @@ Plugins
 
 In order to simulate and compile quantum circuits or perform other complicated electronic structure calculations, one can install OpenFermion plugins. We currently support a circuit simulation plugin for `ProjectQ <https://projectq.ch>`__, which you can find at `OpenFermion-ProjectQ <http://github.com/quantumlib/OpenFermion-ProjectQ>`__. We also support electronic structure plugins for `Psi4 <http://psicode.org>`__, which you can find at `OpenFermion-Psi4 <http://github.com/quantumlib/OpenFermion-Psi4>`__ (recommended), and for `PySCF <https://github.com/sunqm/pyscf>`__, which you can find at `OpenFermion-PySCF <http://github.com/quantumlib/OpenFermion-PySCF>`__.
 
-Authors
--------
-
-`Ryan Babbush <http://ryanbabbush.com>`__ (Google),
-`Jarrod McClean <http://jarrodmcclean.com>`__ (Google),
-`Ian Kivlichan <http://aspuru.chem.harvard.edu/ian-kivlichan/>`__ (Harvard),
-Damian Steiger (ETH Zurich),
-Wei Sun (Google),
-Craig Gidney (Google),
-Thomas Haner (ETH Zurich),
-Hannah Sim (Harvard),
-Vojtech Havlicek (Oxford),
-Kanav Setia (Dartmouth),
-Nicholas Rubin (Rigetti),
-Matthew Neeley (Google) and
-Dave Bacon (Google).
-
-
 How to contribute
 -----------------
 
 We'd love to accept your contributions and patches to OpenFermion.
-There are a few small guidelines you need to follow. 
-
+There are a few small guidelines you need to follow.
 Contributions to OpenFermion must be accompanied by a Contributor License Agreement.
 You (or your employer) retain the copyright to your contribution,
 this simply gives us permission to use and redistribute your contributions as part of the project.
@@ -77,11 +58,29 @@ more information on using pull requests.
 Furthermore, please make sure your new code comes with extensive tests!
 We use automatic testing to make sure all pull requests pass tests and do not
 decrease overall test coverage by too much. Make sure you adhere to our style
-guide. Just have a look at our code for clues. We mostly follow pep8 and use
-the pep8 linter to check for it. Code should always come with documentation,
-which is generated automatically and can be found
+guide. Just have a look at our code for clues. We mostly follow
+`PEP 8 <https://www.python.org/dev/peps/pep-0008/>`_ and use
+the corresponding `linter <https://pypi.python.org/pypi/pep8>`_ to check for it.
+Code should always come with documentation, which is generated automatically and can be found
 `here <http://openfermion.readthedocs.io/en/latest/openfermion.html>`_.
 
+Authors
+-------
+
+`Ryan Babbush <http://ryanbabbush.com>`__ (Google),
+`Jarrod McClean <http://jarrodmcclean.com>`__ (Google),
+`Ian Kivlichan <http://aspuru.chem.harvard.edu/ian-kivlichan/>`__ (Harvard),
+Damian Steiger (ETH Zurich),
+Wei Sun (Google),
+Craig Gidney (Google),
+Thomas Haner (ETH Zurich),
+Hannah Sim (Harvard),
+Vojtech Havlicek (Oxford),
+Kanav Setia (Dartmouth),
+Nicholas Rubin (Rigetti),
+Matthew Neeley (Google) and
+Dave Bacon (Google).
+
 Questions?
 ----------