Fix typos (#598)

* Updating Data Sources pages

* first drafts of entity import

* more work on entities

* continued work

* continued work

* allow sample API key

* more work

* more work on entities

* more work

* more changes

* more changes

* split out custom entities into a separate file

* start work on Python v2 docs

* start of new Python docs

* create all pages for directory and more work on landing page

* more work

* add skeleton files

* rename old Python docs

* fix mistaken files

* fix files again

* fix more files

* remove template from PR

* changed examples to directly print responses

* move pagination out of main page and into node page

* wording change suggested by Jorge

* fixed response formatting object wording, per Jorge

* fix package name

* set to unpublished

* set back to published

* new node page

* rewrote response formatting section for new methods

* Removed node.md because of unresolvable merge conflict.

* corrected package name

* Update api/python/v2/node.md

* fix typos

Author: kmoscoe

api/python/v2/index.md

@@ -46,13 +46,13 @@ This procedure uses a Python virtual environment as recommended by Google Cloud
 1. Install the the `datacommons-client` package:
 
    ```bash
-   $ pip install datacommons_client
+   $ pip install datacommons-client
    ```
 
 To get additional functionality with Pandas DataFrames, run:
 
 ```bash
-$ pip install "datacommons_client[Pandas]"
+$ pip install "datacommons-client[Pandas]"
 ```
 ## Run Python interactively
 
@@ -267,4 +267,4 @@ Response:
 > **Note:** On the endpoint reference pages we will show all responses using this format, but will leave out the response methods for succinctness.
 
 <script src="/assets/js/syntax_highlighting.js"></script>
-<script src="/assets/js/api-doc-tabs.js"></script>
+<script src="/assets/js/api-doc-tabs.js"></script>

api/python/v2/resolve.md

@@ -107,7 +107,7 @@ fetch(node_ids, expression)
 | Name          | Type  |   Description  |
 |---------------|-------|----------------|
 | node_ids <br /> <required-tag>Required</required-tag>  | string or list of strings | A term or list of terms that identify each node to search for, such as their name. |
-| expression <br /> <required-tag>Required</required-tag> | string | An expression that describes the identifier used in the `node_ids` parameter. Only three are currently supported: <br />`<-description`: Search for nodes based on name-related properties (such as `name`, `alternateName`, etc.).<br/>`<-wikidataId`: Search for nodes based on their Wikidata ID(s).<br/>`<-geoCoordinates`: Search for nodes based on latitude and/or longitude.<br/> Note that these are not necessarily "properties" that appear in the knowledge graph; instead, they are "synthetic" attributes that cover searches over multiple properties. <br/>Each expression must end with `->dcid` and my optionally include a [`typeOf` filter](/api/rest/v2/index.html#filters). |
+| expression <br /> <required-tag>Required</required-tag> | string | An expression that describes the identifier used in the `node_ids` parameter. Only three are currently supported: <br />`<-description`: Search for nodes based on name-related properties (such as `name`, `alternateName`, etc.).<br/>`<-wikidataId`: Search for nodes based on their Wikidata ID(s).<br/>`<-geoCoordinates`: Search for nodes based on latitude and/or longitude.<br/> Note that these are not necessarily "properties" that appear in the knowledge graph; instead, they are "synthetic" attributes that cover searches over multiple properties. <br/>Each expression must end with `->dcid` and may optionally include a [`typeOf` filter](/api/rest/v2/index.html#filters). |
 {: .doc-table }
 
 ### Examples
@@ -431,4 +431,4 @@ Response:
    ]
 }
 ```
-{: .example-box-content .scroll}
+{: .example-box-content .scroll}

api/rest/v2/resolve.md

@@ -73,7 +73,7 @@ JSON data:
 |---------------|-------|----------------|
 | key <br /> <required-tag>Required</required-tag> | string | Your API key. See the [section on authentication](/api/rest/v2/index.html#authentication) for details. |
 | nodes <br /> <required-tag>Required</required-tag>  | list of strings | A list of terms that identify each node to search for, such as their names. |
-| property <br /> <required-tag>Required</required-tag> | string | An expression that describes the identifier used in the `nodes` parameter. Only three are currently supported:<br />`<-description`: Search for nodes based on name-related properties (such as `name`, `alternateName`, etc.).<br/>`<-wikidataId`: Search for nodes based on their Wikidata ID(s).<br/>`<-geoCoordinates`: Search for nodes based on latitude and/or longitude.<br/>Note that these are not necessarily "properties" that appear in the knowledge graph; instead, they are "synthetic" attributes that cover searches over multiple properties. <br/>Each expression must end with `->dcid` and my optionally include a [`typeOf` filter](/api/rest/v2/index.html#filters). |
+| property <br /> <required-tag>Required</required-tag> | string | An expression that describes the identifier used in the `nodes` parameter. Only three are currently supported:<br />`<-description`: Search for nodes based on name-related properties (such as `name`, `alternateName`, etc.).<br/>`<-wikidataId`: Search for nodes based on their Wikidata ID(s).<br/>`<-geoCoordinates`: Search for nodes based on latitude and/or longitude.<br/>Note that these are not necessarily "properties" that appear in the knowledge graph; instead, they are "synthetic" attributes that cover searches over multiple properties. <br/>Each expression must end with `->dcid` and may optionally include a [`typeOf` filter](/api/rest/v2/index.html#filters). |
 {: .doc-table }
 
 ## Response