From 1c649d90da1aefd4dd648f735dc89053da7556a7 Mon Sep 17 00:00:00 2001
From: Adam Caprez <acaprez2@unl.edu>
Date: Thu, 8 Aug 2019 21:12:04 +0000
Subject: [PATCH] Fix links.
---
CONTRIBUTING.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1bf27c62..79ecb43b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -20,14 +20,14 @@ to tell us about a spelling mistake,
some awkward wording,
or a factual error.
-1. If you do not have access to [UNL's GitLab instance][http://git.unl.edu],
- you can [send us comments by email][contact].
+1. If you do not have access to [UNL's GitLab instance](http://git.unl.edu),
+ you can [send us comments by email](mailto:hcc-support@unl.edu).
However,
we will be able to respond more quickly if you use one of the other methods described below.
-2. If you have access to [UNL's GitLab instance][http://git.unl.edu],
+2. If you have access to [UNL's GitLab instance](http://git.unl.edu),
but do not know how to use Git,
- you can report problems or suggest improvements by [creating an issue][issues].
+ you can report problems or suggest improvements by [creating an issue](https://git.unl.edu/hcc/hcc-docs/issues/new).
This allows us to assign the item to someone
and to respond to it in a threaded discussion. Detailed information on creating
issues can be found in the [GitLab Documentation](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html)
@@ -39,7 +39,7 @@ or a factual error.
## Where to Contribute
-1. Checking for outstanding [issues](issues) is a quick way to identify contribution areas. Additionally,
+1. Checking for outstanding [issues](https://git.unl.edu/hcc/hcc-docs/issues) is a quick way to identify contribution areas. Additionally,
review an comments on existing merge requests are welcome.
2. All documentation content can be found within the `content` folder. Subdirectories indicate menu items,
@@ -52,7 +52,7 @@ adhere to [UNL style guidelines](https://wdn.unl.edu/unl-web-framework-5-standar
There are many ways to contribute,
from contributing additional documentation topics or submitting software specific job examples,
-to updating or adding to existing documentation and submitting [bug reports][issues]
+to updating or adding to existing documentation and submitting [bug reports](https://git.unl.edu/hcc/hcc-docs/issues)
about things that don't work, aren't clear, or are missing.
Comments on issues and reviews of pull requests are just as welcome:
--
GitLab