From 10e33e334df9202cd8c8a940c7cd3ec36548d7d8 Mon Sep 17 00:00:00 2001 From: seabeepea Date: Sun, 9 Jun 2019 16:40:08 -0700 Subject: [PATCH] typos --- CONTRIBUTING.md | 14 +++++--------- README.md | 10 +++++----- 2 files changed, 10 insertions(+), 14 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 933e850a29..645a679b09 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -70,12 +70,10 @@ Documentation](https://git-scm.com/doc). Once your Git environment is operational, the next step is to locally **clone** your forked OpenColorIO repository, and add a **remote** pointing to the upstream OpenColorIO repository. These topics are -covered in [Cloning a repository] -(https://help.github.com/articles/cloning-a-repository/) and -[Configuring a remote for a fork] -(https://help.github.com/articles/configuring-a-remote-for-a-fork/), +covered in [Cloning a repository](https://help.github.com/articles/cloning-a-repository/) and +[Configuring a remote for a fork](https://help.github.com/articles/configuring-a-remote-for-a-fork/), but again, if you need assistance feel free to reach out on the -openexr-dev mail list. +openexr-dev@lists.aswf.io mail list. ## Contributor Licence Agreements @@ -89,14 +87,12 @@ project leader, but anything complex requires a CLA. * If you are an individual writing the code on your own time and you're SURE you are the sole owner of any intellectual property you -contribute, use the [Individual Contributor License Agreement] -(http://www.openexr.com/downloads/OpenEXRIndividualContributorLicenseAgreement.docx). +contribute, use the [Individual Contributor License Agreement](http://www.openexr.com/downloads/OpenEXRIndividualContributorLicenseAgreement.docx). * If you are writing the code as part of your job, or if there is any possibility that your employers might think they own any intellectual property you create, then you should use the [Corporate Contributor -Licence Agreement] -(http://www.openexr.com/downloads/OpenEXRCorporateContributorLicenseAgreement.docx). +Licence Agreement](http://www.openexr.com/downloads/OpenEXRCorporateContributorLicenseAgreement.docx). Download the appropriate CLA from the links above (or find them in the src/doc directory of the software distribution), print, sign, and diff --git a/README.md b/README.md index 307d2374a7..ebaf7b88bc 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ OpenEXR's features include: ## License OpenEXR, including all contributions, is released under a modified BSD -license. Please see the [LICENSE.md] (LICENSE.md) file accompanying +license. Please see the [LICENSE.md](LICENSE.md) file accompanying the distribution for the legal fine print. ## OpenEXR Sub-modules @@ -79,23 +79,23 @@ GitHub repository: http://www.github.com/openexr/openexr Deverloper discussion mailing list: -* [openexr-dev@lists.aswf.io] (https://lists.aswf.io/g/openexr-dev) +* [openexr-dev@lists.aswf.io](https://lists.aswf.io/g/openexr-dev) ## Building and Installation Download the latest release of OpenEXR from the GitHub Releases page: https://github.com/openexr/openexr/releases. -For more information about building from sources, see the [INSTALL.md] (INSTALL.md) file. +For more information about building from sources, see the [INSTALL.md](INSTALL.md) file. ## Contributing -See [CONTRIBUTING.md] (CONTRIBUTING.md) for more information about contributing to OpenEXR. +See [CONTRIBUTING.md](CONTRIBUTING.md) for more information about contributing to OpenEXR. ## Project Goverance OpenEXR is owned by the Academy Software Foundation, and is maintained -by the developer community. See [GOVERNANCE.md] (GOVERNANCE.md) for +by the developer community. See [GOVERNANCE.md](GOVERNANCE.md) for more infomation. ## Documentation