Revised documentation.

Author: hcpchris

docs/_versus_alternatives.rst

@@ -10,7 +10,7 @@ compare it against some commonly-used alternatives:
 
     By far, this is the most common approach to integrating Highcharts into your Python
     code. As a developer, you know that your JavaScript front-end will be using Highcharts
-    (JS)). So you work in your Python backend to deliver the data to your front-end that your
+    (JS). So you work in your Python backend to deliver the data to your front-end that your
     front-end will need.
 
     There are many patterns for rolling your own Highcharts + Python implementation, but

docs/contributing.rst

@@ -216,8 +216,8 @@ Design Patterns and Standards
 ***************************************************
 
 `Highcharts (JS) <https://www.highcharts.com>`__ is a large, robust, and complicated
-JavaScript library. If in doubt, take a look at their extensive
-`documentation <https://www.highcharts.com/docs/index>`_ and in particular their
+JavaScript library. If in doubt, take a look at the extensive
+`documentation <https://www.highcharts.com/docs/index>`_ and in particular the
 `API reference <https://api.highcharts.com/highcharts>`_. Because
 **Highcharts for Python** wraps the Highcharts JS API, its design is heavily shaped by
 Highcharts JS' own design - as one should expect.

docs/toolkit.rst

@@ -14,8 +14,8 @@ The Toolkit's Contents
 
 The **Highcharts for Python Toolkit** features a number of separate Python
 libraries which extend the core **Highcharts Core for Python** (``highcharts-core``) library.
-This pattern maps quite naturally to the Highcharts JS design, where multiple
-other modules extend the core Highcharts JS library.
+This pattern maps quite naturally to the Highcharts (JS) design, where multiple
+other modules extend the core Highcharts (JS) library.
 
 The **Highcharts for Python Toolkit** includes two categories of tools: