From 8c4576b9b6423e3b4cc17743e1edb8d39c6a9918 Mon Sep 17 00:00:00 2001 From: Kenan Erdogan Date: Fri, 11 Jan 2019 15:23:03 +0100 Subject: [PATCH] minor fixes in documentation --- doc/index.rst | 2 +- doc/overview.rst | 4 ++-- doc/turn-off.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/index.rst b/doc/index.rst index 10dc55139..63b9903c7 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -11,7 +11,7 @@ Getting started The primary goal of BinderHub is creating custom computing environments that can be used by many remote users. BinderHub enables an end user to easily -specify a desired computing environment from a GitHub repo. BinderHub then +specify a desired computing environment from a Git repo. BinderHub then serves the custom computing environment at a URL which users can access remotely. diff --git a/doc/overview.rst b/doc/overview.rst index e978487e1..b4f478459 100644 --- a/doc/overview.rst +++ b/doc/overview.rst @@ -17,9 +17,9 @@ and registry of Docker images. It utilizes the following tools: - **Kubernetes** to manage resources on the cloud - **Helm** to configure and control Kubernetes - **Docker** to use containers that standardize computing environments -- A **BinderHub UI** that users can access to specify GitHub repos they want +- A **BinderHub UI** that users can access to specify Git repos they want built -- **BinderHub** to generate Docker images using the URL of a GitHub repository +- **BinderHub** to generate Docker images using the URL of a Git repository - A **Docker registry** (such as gcr.io) that hosts container images - **JupyterHub** to deploy temporary containers for users diff --git a/doc/turn-off.rst b/doc/turn-off.rst index b63740f67..74ab67ba3 100644 --- a/doc/turn-off.rst +++ b/doc/turn-off.rst @@ -10,7 +10,7 @@ Contracting the size of your cluster ------------------------------------ If you would like to shrink the size of your cluster, refer to the -`Expanding and contracting the size of your cluster `_ +`Expanding and contracting the size of your cluster `_ section of the `Zero to JupyterHub`_ documentation. Resizing the cluster to zero nodes could be used if you wish to temporarily reduce the cluster (and save costs) without deleting the cluster.