Remove glossary content and make necessary doc edits to clarify terms

This after reviewing each and every glossary entry to ensure it was
covered in GitLab docs, or about.gitlab, or not needed.

doc/university/README.md

@@ -78,7 +78,6 @@ The GitLab University curriculum is composed of GitLab videos, screencasts, pres
 
 ### 1.8 GitLab Training Material
 
-1. [Git and GitLab Terminology](glossary/README.md)
 1. [Git and GitLab Workshop - Slides](https://docs.google.com/presentation/d/1JzTYD8ij9slejV2-TO-NzjCvlvj6mVn9BORePXNJoMI/edit?usp=drive_web)
 
 ## 2. GitLab Intermediate

doc/user/instance_statistics/convdev.md

@@ -5,7 +5,7 @@
 NOTE: **Note:**
 Your GitLab instance's [usage ping](../admin_area/settings/usage_statistics.md#usage-ping-core-only) must be activated in order to use this feature.
 
-The Conversational Development Index (ConvDev Index) gives you an overview of your entire
+The [Conversational Development](http://conversationaldevelopment.com/2017/04/16/what-is-conversational-development/) Index (ConvDev Index) gives you an overview of your entire
 instance's adoption of [Concurrent DevOps](https://about.gitlab.com/concurrent-devops/)
 from planning to monitoring.
 

doc/user/project/cycle_analytics.md

 # Cycle Analytics
 
-> [Introduced][ce-5986] in GitLab 8.12. Further features were added in GitLab
-  8.14.
-
-Cycle Analytics measures the time spent to go from an [idea to production] for
-each of your projects. Cycle Analytics displays the median time for an idea to
+Cycle Analytics measures the time spent to go from an [idea to production] - also known
+as cycle time - for each of your projects. Cycle Analytics displays the median time for an idea to
 reach production, along with the time typically spent in each DevOps stage along the way.
 
 Cycle Analytics is useful in order to quickly determine the velocity of a given