git commit: docs: fix a typo.

[to...@apache.org]

Updated Branches:
  refs/heads/trunk cfe46bf7d -> 2317df32c


docs: fix a typo.


Project: http://git-wip-us.apache.org/repos/asf/libcloud/repo
Commit: http://git-wip-us.apache.org/repos/asf/libcloud/commit/2317df32
Tree: http://git-wip-us.apache.org/repos/asf/libcloud/tree/2317df32
Diff: http://git-wip-us.apache.org/repos/asf/libcloud/diff/2317df32

Branch: refs/heads/trunk
Commit: 2317df32c3246f15b2d2ca635f59ddafb055796e
Parents: cfe46bf
Author: Tomaz Muraus <to...@apache.org>
Authored: Tue Nov 5 08:50:51 2013 +0000
Committer: Tomaz Muraus <to...@apache.org>
Committed: Tue Nov 5 08:53:49 2013 +0000

----------------------------------------------------------------------
 docs/compute/pricing.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/libcloud/blob/2317df32/docs/compute/pricing.rst
----------------------------------------------------------------------
diff --git a/docs/compute/pricing.rst b/docs/compute/pricing.rst
index b0620d4..8bed66f 100644
--- a/docs/compute/pricing.rst
+++ b/docs/compute/pricing.rst
@@ -14,14 +14,14 @@ Example bellow shows how to retrieve pricing for ``NodeSize`` objects using
    :language: python
    :emphasize-lines: 11-19
 
-As noted above this pricing information is an estimate and you should only
+As noted above this pricing information is an estimate and should only
 be used as such. You should always check your provider website / control panel
 for accurate pricing information and never rely solely on Libcloud pricing data.
 
 Besides that, many cloud providers also offer different pricing scheme based
-on the volume and discounts for reserved instances. All of this information
-is not taken into account in the simplistic "price per hour" pricing scheme
-available in Libcloud.
+on the volume, term commitment and discounts for reserved instances. All of
+this information is not taken into account in the simplistic "price per hour"
+pricing scheme available in Libcloud.
 
 Where does the Libcloud pricing data come from?
 -----------------------------------------------
@@ -30,8 +30,8 @@ Most of the providers don't provide pricing information via the API which means
 most of the pricing information is scrapped directly from the provider
 websites.
 
-Pricing data which is scrapped from the provider websites is located in the
-a JSON file (``data/pricing.json``) which is bundled with each release. This
+Pricing data which is scrapped from the provider websites is located in a
+JSON file (``data/pricing.json``) which is bundled with each release. This
 pricing data is only updated once you install a new release which means it
 could be out of date.
 
@@ -46,7 +46,7 @@ Using a custom pricing file
 
 By default Libcloud reads pricing data from ``data/pricing.json`` file which
 is included in the release package. If you want to use a custom pricing file,
-simply put move the file to ``~/.libcloud.pricing.json``.
+simply move your custom pricing file to ``~/.libcloud.pricing.json``.
 
 If ``~/.libcloud.pricing.json`` file is available, Libcloud will use it instead
 of the default pricing file which comes bundled with the release.