From 8acd09f01228eb4d40a487ad8de12ff032068b07 Mon Sep 17 00:00:00 2001
From: dillonwi <46857484+dillonwi@users.noreply.github.com>
Date: Tue, 21 May 2019 22:51:55 -0600
Subject: [PATCH] Added links to technical guidance.

I have added some links to technical guidance on how to make a fork/pull request on Github. These have been added for the convenience of first time Github users, and may help foster contributions from new programmers or students.
---
 CONTRIBUTING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3e0558e07f..1251b153e9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -25,12 +25,12 @@ accept your pull requests.
 1. The repo owner will respond to your issue promptly.
 1. If your proposed change is accepted, and you haven't already done so, sign a
    Contributor License Agreement (see details above).
-1. Fork the desired repo, develop and test your code changes.
+1. Fork the desired repo, develop and test your code changes. (For technical guidance on how to fork a repo on Github, see https://help.github.com/en/articles/fork-a-repo)
 1. Ensure that your code adheres to the existing style in the sample to which
    you are contributing. Refer to the
    [Google Cloud Platform Samples Style Guide]
    (https://github.com/GoogleCloudPlatform/Template/wiki/style.html) for the
    recommended coding standards for this organization.
 1. Ensure that your code has an appropriate set of unit tests which all pass.
-1. Submit a pull request.
+1. Submit a pull request. (For technical guidance on how to submit a pull request on Github, see https://help.github.com/en/articles/creating-a-pull-request)