fix typos Contributing.md
@@ -16,7 +16,7 @@ https://groups.google.com/forum/#!forum/altair-viz. If you are working on
Altair, you can talk to other developers in the `#altair` channel of the [Vega
slack](https://bit.ly/join-vega-slack).
-## How To Contribute Code to Alatir
+## How To Contribute Code to Altair
### Setting Up Your Environment
@@ -58,14 +58,14 @@ and running black on the local directory:
$ pip install black
$ black .
```
-When you are happy with your changes, you can commit them to your branch by runing
+When you are happy with your changes, you can commit them to your branch by running
```
$ git add <modified-file>
$ git commit -m "Some descriptive message about your change"
$ git push origin <branch-name>
```
Finally you will need to submit a pull request (PR) on GitHub asking to merge
-your example branch into altair master. For details on creating a PR see GitHub
+your example branch into Altair master. For details on creating a PR see GitHub
documentation [Creating a pull
request](https://help.github.com/en/articles/creating-a-pull-request). You can
add more details about your example in the PR such as motivation for the
@@ -116,7 +116,7 @@ Every example should:
The easiest way to get started would be to adapt examples from the [Vega-Lite
example gallery](https://vega.github.io/vega-lite/examples/) which are missing
-in the altair gallery. Or you can feel free to be creative and build your own
+in the Altair gallery. Or you can feel free to be creative and build your own
visualizations.
Often it is convenient to draft an example outside of the main repository, such
@@ -134,8 +134,8 @@ Some additional notes:
a title in the docstring underlined with `---`, and be sure that the size of
the underline exactly matches the size of the title text.
- If your example fits into a chart type but involves significant configuration
- it should be in the `case studies` category. If your example doesn't fit well
- into any category then it can be included in the `other charts` category.
+ it should be in the `Case Studies` category. If your example doesn't fit well
+ into any category then it can be included in the `Other Charts` category.
- For consistency all data used for a visualization should be assigned to the
variable `source`. Then `source` is passed to the `alt.Chart` object. See
other examples for guidance.
@@ -149,6 +149,6 @@ Some additional notes:
data.movies.url`. This is to ensure that Altair's automated test suite does
not depend on availability of external HTTP resources.
-Note that examples shown on the [altair website](https://altair-viz.github.io/)
+Note that examples shown on the [Altair website](https://altair-viz.github.io/)
are only updated when a new version is released so your new example might not show
up there for a while.
