diff --git a/content/quickstarts/connecting/_index.md b/content/quickstarts/connecting/_index.md
index b0149d21ca0095c145057e8f14414d104e7132af..f4ad513d67505bd09926cec15c1438608c27ec01 100644
--- a/content/quickstarts/connecting/_index.md
+++ b/content/quickstarts/connecting/_index.md
@@ -3,18 +3,8 @@ title = "How to Connect"
 description = "What is a cluster and what is HPC"
 weight = "9"
 +++
-High-Performance Computing is the use of groups of computers to solve computations a user or group would not be able to solve in a reasonable time-frame on their own desktop or laptop. This is often achieved by splitting one large job amongst numerous cores or 'workers'. This is similar to how a skyscraper is built by numerous individuals rather than a single person. Many fields take advantage of HPC including bioinformatics, chemistry, materials engineering, and newer fields such as educational psychology and philosophy.
-{{< figure src="/images/cluster.png" height="450" >}}
-HPC clusters consist of four primary parts, the login node, management node, workers, and a central storage array. All of these parts are bound together with a scheduler such as HTCondor or SLURM. 
-</br></br>
-#### Login Node:
-Users will automatically land on the login node when they log in to the clusters. You will [submit jobs] ({{< ref "/guides/submitting_jobs" >}}) using one of the schedulers and pull the results of your jobs. Running jobs on the login node directly will be stopped so others can use the login node to submit jobs.
-</br></br>
-#### Management Node: 
-The management node does as it sounds, it manages the cluster and provides a central point to manage the rest of the systems.
-</br></br>
-#### Worker Nodes:
-The worker nodes are what run and process your jobs that are submitted from the schedulers. Through the use of the schedulers, more work can be efficiently done by squeezing in all jobs possible for the resources requested throughout the nodes. They also allow for fair use computing by making sure one user or group is not using the entire cluster at once and allowing others to use the clusters.
-</br></br> 
-#### Central Storage Array:
-The central storage array allows all of the nodes within the cluster to have access to the same files without needing to transfer them around. HCC has three arrays mounted on the clusters with more details [here]({{< ref "/guides/handling_data" >}}).
+Connecting to one of our clusters is very simple. In a terminal or command prompt, type `ssh <username>@crane.unl.edu` and the corresponding password to get access to the HCC cluster **Crane**.
+{{< highlight bash >}}
+$ ssh <username>@crane.unl.edu
+$ <password>
+{{< /highlight >}}
diff --git a/content/quickstarts/hpc_intro.md b/content/quickstarts/hpc_intro.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b05136d9e871bff17bf4328fdea4e0e1d77ab0b
--- /dev/null
+++ b/content/quickstarts/hpc_intro.md
@@ -0,0 +1,22 @@
++++
+title = "Introduction to HPC"
+description = "What is a cluster and what is HPC"
+weight = "1"
++++
+High-Performance Computing is the use of groups of computers to solve computations that a user or group would not be able to solve in a reasonable time-frame on their own desktop or laptop. This is often achieved by splitting one large job amongst numerous cores or 'workers'. This is similar to how a skyscraper is built by numerous individuals rather than a single person. Many fields take advantage of HPC including bioinformatics, chemistry, materials engineering, and newer fields such as educational psychology and philosophy.
+
+HPC clusters consist of four primary parts, the login node, management node, workers, and a central storage array. The cullmination of these parts create a high performance cluster that can recieve work from the schedulers.
+{{< figure src="/images/cluster.png" height="450" >}}
+##### [Source](https://training.h3abionet.org/technical_workshop_2015/?page_id=403)
+
+#### Login Node:
+Users will automatically land on the login node when they log in to the clusters. You will [submit jobs] ({{< ref "/quickstarts/submitting_jobs" >}}) using one of the schedulers and pull the results of your jobs. Running jobs on the login node directly will be stopped so others can use the login node to submit jobs.
+</br></br>
+#### Management Node: 
+The management node contains and runs the schedulers and other utilities for managing the cluster.
+</br></br>
+#### Worker Nodes:
+The worker nodes are what run and process your jobs that are submitted from the schedulers. Through the use of the schedulers, more work can be efficiently done by squeezing in all jobs possible for the resources requested throughout the nodes. They also allow for fair use computing by making sure one user or group is not using the entire cluster at once and allowing others to use the clusters.
+</br></br> 
+#### Central Storage Array:
+The central storage array allows all of the nodes within the cluster to have access to the same files without needing to transfer them around. HCC has three arrays mounted on the clusters with more details [here]({{< ref "/guides/handling_data" >}}).
\ No newline at end of file
diff --git a/content/quickstarts/setting_up_and_using_duo.md b/content/quickstarts/setting_up_and_using_duo.md
index 04f0847dc6979387f136f44fe301904ad152c419..61218e53e4fc2eefeb5119b8b4aafaa919657def 100644
--- a/content/quickstarts/setting_up_and_using_duo.md
+++ b/content/quickstarts/setting_up_and_using_duo.md
@@ -75,11 +75,11 @@ this example, the choices are Duo Push notification, SMS message, or
 phone call. Choosing option 1 for Duo Push, a request to verify the
 login will be sent to the user's smartphone.
 
-{{< figure src="/images/5832716.png" height="350" >}}
+{{< figure src="/images/DUORequest.jpg" height="350" >}}
 
 Simply tap `Approve` to verify the login.
 
-{{< figure src="/images/5832717.png" height="350" >}}
+{{< figure src="/images/DUOApprove.jpg" height="350" >}}
 
 {{% notice warning%}}**If you receive a verification request you didn't initiate, deny the 
 request and contact HCC immediately via email at
diff --git a/static/images/5832716.png b/static/images/5832716.png
deleted file mode 100644
index 831f07225445bcdcd15dbae25004b205aee279d7..0000000000000000000000000000000000000000
Binary files a/static/images/5832716.png and /dev/null differ
diff --git a/static/images/5832717.png b/static/images/5832717.png
deleted file mode 100644
index c64d22e4caf01bb59f86f1a530d5c3dc369e1d8d..0000000000000000000000000000000000000000
Binary files a/static/images/5832717.png and /dev/null differ
diff --git a/static/images/DUOApprove.jpg b/static/images/DUOApprove.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3867d9705f59b7553096b347c3356eb64d596b2e
Binary files /dev/null and b/static/images/DUOApprove.jpg differ
diff --git a/static/images/DUORequest.jpg b/static/images/DUORequest.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7bb783c573e4a38e69818f4376b1630a1bd7f9ad
Binary files /dev/null and b/static/images/DUORequest.jpg differ