update README to reflect PVLIB_Python name change

Author: wholmgren

README.md

@@ -1,27 +1,29 @@
-pythonic-PVLIB
-==============
+PVLIB_Python
+============
 
-pythonic-PVLIB is a fork of the [PVLIB_Python](https://github.com/Sandia-Labs/PVLIB_Python) project.
+This repo is a fork of the [Sandia PVLIB_Python](https://github.com/Sandia-Labs/PVLIB_Python) project.
 
 It provides a set of sometimes-well-documented and usually correct functions for simulating the performance of photovoltaic energy systems. The toolbox was originally developed at Sandia National Laboratories and it implements many of the models and methods developed at the Labs. 
 
-We make some contributions to the PVLIB\_Python develop branch, and we pull some commits to PVLIB\_Python back into our fork. We hope that the Sandia PVLIB_Python becomes the community standard, but we had some different ideas about how things should be done and we needed to make progress faster than the collaborative cycle would allow. See below for a partial list of differences. 
+We make some contributions to the Sandia develop branch, and we pull some commits back into our fork. We hope that the Sandia PVLIB_Python becomes the community standard, but we had some different ideas about how things should be done and we needed to make progress faster than the collaborative cycle would allow. See below for a partial list of differences. 
 
-We use this library to generate solar power forecasts for TEP, APS, and SVERI utilities, and to perform grid integration and variability studies for SVERI utilities. For more information, see [https://forecasting.uaren.org](https://forecasting.uaren.org) and [https://sveri.uaren.org](https://sveri.uaren.org).
+We use this library to generate solar power forecasts for TEP, APS, and other SVERI utilities, and to perform grid integration and variability studies for SVERI. For more information, see [https://forecasting.uaren.org](https://forecasting.uaren.org) and [https://sveri.uaren.org](https://sveri.uaren.org).
 
-The primary drawback to using this library over the official library is that, well, it's not the official Sandia library. Another drawback is that the structure of this library will look a lot different to people coming from the MATLAB world, which is either a good thing or a bad thing depending on your perspective. Keep the following in mind as you consider using or developing pythonic-PVLIB:
+The primary drawback to using this library over the official library is that, well, it's not the official Sandia library. Another drawback is that the structure of this library will look a lot different to people coming from the MATLAB world, which is either a good thing or a bad thing depending on your perspective. Keep the following in mind as you consider using or developing our fork:
 
-* We hope to keep the projects as similar as possible to make it easier for people to experiment with pythonic-PVLIB. 
+* We hope to keep the projects as similar as possible to make it easier for people to experiment with our fork. 
 * The Sandia repo should be the default repo for the user community.
-* Developers should strongly consider working on the official Sandia repo rather than, or in addition to, pythonic-PVLIB.
+* Developers should strongly consider working on the official Sandia repo rather than, or in addition to, our fork.
 * Reread the above point (...waiting...) before the following (...waiting again...): community contributions in the form of PRs, issues, wikis, docs, tutorials, thoughts, etc are all welcomed and we will try hard to address them in a timely manner.
 * All code contributions must be documented, PEP8 compliant, and python 3 compatible.
 * We're not promising to maintain this repo for any length of time. 
 
+That being said, we welcome your thoughts and contributions to our fork.
+
 
 Code differences
 ===============
-Here are some of the major differences between our fork and PVLIB\_Python. Note that some of these differences have been resolved in the PVLIB\_Python [develop branch](https://github.com/Sandia-Labs/PVLIB_Python/tree/develop).
+Here are some of the major differences between our fork and the official project. Note that some of these differences have been resolved in the Sandia [develop branch](https://github.com/Sandia-Labs/PVLIB_Python/tree/develop).
 
 * Remove pvl_ from module names.
 * Locations are now ``pvlib.location.Location`` objects, not structs.