Fixed bad linked in back ticks

Author: seanlaw

docs/Contribute.ipynb

@@ -40,7 +40,7 @@
    "source": [
     "## Find your contribution\n",
     "\n",
-    "You've decided that you want to contribute, but how do you approach a new project and figure out where you can help? This will feel like like trying to jump into a conversation that's been happening for months (or years) and can often be intimidating. If you've used the project before, you'll be more familiar with its structure and API, but you probably haven't \"peeked behind the curtain\" before. The best place to get started is the list of [Issues](https://github.com/TDAmeritrade/stumpy/issues). These are requests/changes/bugs that other people have identified. Feel free to peruse the list to get a feel for all of the work ongoing in the project. Often, maintainers will have a label system to organize the issues. These labels may include things like `documentation` or `enhancement`. For new contributors, many projects have a [`good first issue` label](https://github.com/TDAmeritrade/stumpy/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).\n",
+    "You've decided that you want to contribute, but how do you approach a new project and figure out where you can help? This will feel like like trying to jump into a conversation that's been happening for months (or years) and can often be intimidating. If you've used the project before, you'll be more familiar with its structure and API, but you probably haven't \"peeked behind the curtain\" before. The best place to get started is the list of [Issues](https://github.com/TDAmeritrade/stumpy/issues). These are requests/changes/bugs that other people have identified. Feel free to peruse the list to get a feel for all of the work ongoing in the project. Often, maintainers will have a label system to organize the issues. These labels may include things like `documentation` or `enhancement`. For new contributors, many projects have a [good first issue label](https://github.com/TDAmeritrade/stumpy/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).\n",
     "\n",
     "Your next stop (if it exists), should always be [CONTRIBUTING.md](https://github.com/TDAmeritrade/stumpy/blob/master/CONTRIBUTING.md). Here, the maintainers outline any guidance they have for contributors,\n",
     "\n",
@@ -90,7 +90,7 @@
     "\n",
     "When working on a new project, there are often going to be dependencies. In order to isolate dependencies between different projects, it's a good practice to use a virtual environment. STUMPY supports both [venv](https://docs.python.org/3/library/venv.html) and [conda](https://docs.conda.io/en/latest/). After creating and activating either of these virtual environments, any dependencies you install will be isolated (so they don't break anything else on your system).\n",
     "\n",
-    "Next, install the dependencies using the [`From source` Section](https://stumpy.readthedocs.io/en/latest/install.html#from-source) of the instructions. A good check to make sure everything is working 100% is to run the unit tests. For STUMPY, we have scripts to help you do that. You'll run `./setup.sh && ./test.sh`. Ideally, you'll see the excellent STUMPY test coverage passing. If things start failing or breaking, you have a dependency problem. There's nothing worse than finding this out *after* you've made changes.\n",
+    "Next, install the dependencies using the [From Source Section](https://stumpy.readthedocs.io/en/latest/install.html#from-source) of the instructions. A good check to make sure everything is working 100% is to run the unit tests. For STUMPY, we have scripts to help you do that. You'll run `./setup.sh && ./test.sh`. Ideally, you'll see the excellent STUMPY test coverage passing. If things start failing or breaking, you have a dependency problem. There's nothing worse than finding this out *after* you've made changes.\n",
     "\n",
     "If all of the tests pass, you know that you have a working copy of STUMPY to start your development on. Go ahead and implement your feature or change!\n",
     "\n",