Fix mistakes

fancc · Mar 20, 2020 · c6c14b6 · c6c14b6
1 parent 164729d
commit c6c14b6
Show file tree

Hide file tree

Showing 13 changed files with 154 additions and 157 deletions.
diff --git a/content/de/docs/setup/minikube.md b/content/de/docs/setup/minikube.md
@@ -93,27 +93,27 @@ curl $(minikube service hello-minikube --url)
 Hostname: hello-minikube-7c77b68cff-8wdzq
 
 Pod Information:
-  -no pod information available-
+ -no pod information available-
 
 Server values:
-  server_version=nginx: 1.13.3 - lua: 10008
+ server_version=nginx: 1.13.3 - lua: 10008
 
 Request Information:
-  client_address=172.17.0.1
-  method=GET
-  real path=/
-  query=
-  request_version=1.1
-  request_scheme=http
-  request_uri=http://192.168.99.100:8080/
+ client_address=172.17.0.1
+ method=GET
+ real path=/
+ query=
+ request_version=1.1
+ request_scheme=http
+ request_uri=http://192.168.99.100:8080/
 
 Request Headers:
-  accept=*/*
-  host=192.168.99.100:30674
-  user-agent=curl/7.47.0
+ accept=*/*
+ host=192.168.99.100:30674
+ user-agent=curl/7.47.0
 
 Request Body:
-  -no body in request-
+ -no body in request-
 ```
 
 ```shell

diff --git a/content/en/docs/setup/learning-environment/minikube.md b/content/en/docs/setup/learning-environment/minikube.md
@@ -52,7 +52,7 @@ This brief demo guides you on how to start, use, and delete Minikube locally. Fo
 
 2. Now, you can interact with your cluster using kubectl. For more information, see [Interacting with Your Cluster](#interacting-with-your-cluster).
 
-    Let's create a Kubernetes Deployment using an existing image named `echoserver`, which is a simple HTTP server and expose it on port 8080 using `--port`.
+    Let’s create a Kubernetes Deployment using an existing image named `echoserver`, which is a simple HTTP server and expose it on port 8080 using `--port`.
     ```shell
     kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10
     ```
@@ -72,24 +72,24 @@ This brief demo guides you on how to start, use, and delete Minikube locally. Fo
     ```
 4. The `hello-minikube` Pod is now launched but you have to wait until the Pod is up before accessing it via the exposed Service.
 
-  Check if the Pod is up and running:
-  ```shell
-  kubectl get pod
-  ```
-  If the output shows the `STATUS` as `ContainerCreating`, the Pod is still being created:
-  ```
-  NAME                              READY     STATUS              RESTARTS   AGE
-  hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
-  ```
-  If the output shows the `STATUS` as `Running`, the Pod is now up and running:
-  ```
-  NAME                              READY     STATUS    RESTARTS   AGE
-  hello-minikube-3383150820-vctvh   1/1       Running   0          13s
-  ```
+ Check if the Pod is up and running:
+ ```shell
+ kubectl get pod
+ ```
+ If the output shows the `STATUS` as `ContainerCreating`, the Pod is still being created:
+ ```
+ NAME                              READY     STATUS              RESTARTS   AGE
+ hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
+ ```
+ If the output shows the `STATUS` as `Running`, the Pod is now up and running:
+ ```
+ NAME                              READY     STATUS    RESTARTS   AGE
+ hello-minikube-3383150820-vctvh   1/1       Running   0          13s
+ ```
 5. Get the URL of the exposed Service to view the Service details:
-  ```shell
-  minikube service hello-minikube --url
-  ```
+ ```shell
+ minikube service hello-minikube --url
+ ```
 6. To view the details of your local cluster, copy and paste the URL you got as the output, on your browser.
 
     The output is similar to this:
@@ -119,7 +119,7 @@ This brief demo guides you on how to start, use, and delete Minikube locally. Fo
     Request Body:
         -no body in request-
     ```
-  If you no longer want the Service and cluster to run, you can delete them.
+ If you no longer want the Service and cluster to run, you can delete them.
 7. Delete the `hello-minikube` Service:
     ```shell
     kubectl delete services hello-minikube
@@ -145,7 +145,7 @@ This brief demo guides you on how to start, use, and delete Minikube locally. Fo
     Stopping "minikube"...
     "minikube" stopped.
     ```
-  For more information, see [Stopping a Cluster](#stopping-a-cluster).
+ For more information, see [Stopping a Cluster](#stopping-a-cluster).
 10. Delete the local Minikube cluster:
     ```shell
     minikube delete

diff --git a/content/en/docs/tasks/tools/install-minikube.md b/content/en/docs/tasks/tools/install-minikube.md
@@ -89,7 +89,7 @@ Before using `--driver=none`, consult [this documentation](https://minikube.sigs
 Minikube also supports a `vm-driver=podman` similar to the Docker driver. Podman run as superuser privilege (root user) is the best way to ensure that your containers have full access to any feature available on your system.
 
 {{< caution >}}
-The `podman` driver requires running the containers as root because regular user accounts don't have full access to all operating system features that their containers might need to run.
+The `podman` driver requires running the containers as root because regular user accounts don’t have full access to all operating system features that their containers might need to run.
 {{< /caution >}}
 
 ### Install Minikube using a package
@@ -134,11 +134,11 @@ Make sure you have kubectl installed. You can install kubectl according to the i
 
 If you do not already have a hypervisor installed, install one of these now:
 
-* [HyperKit](https://github.com/moby/hyperkit)
+• [HyperKit](https://github.com/moby/hyperkit)
 
-* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 
-* [VMware Fusion](https://www.vmware.com/products/fusion)
+• [VMware Fusion](https://www.vmware.com/products/fusion)
 
 ### Install Minikube
 The easiest way to install Minikube on macOS is using [Homebrew](https://brew.sh):
@@ -170,9 +170,9 @@ Make sure you have kubectl installed. You can install kubectl according to the i
 
 If you do not already have a hypervisor installed, install one of these now:
 
-* [Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install)
+• [Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install)
 
-* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 
 {{< note >}}
 Hyper-V can run on three versions of Windows 10: Windows 10 Enterprise, Windows 10 Professional, and Windows 10 Education.

diff --git a/content/fr/docs/setup/learning-environment/minikube.md b/content/fr/docs/setup/learning-environment/minikube.md
@@ -5,7 +5,7 @@ content_template: templates/concept
 
 {{% capture overview %}}
 
-Minikube est un outil facilitant l'exécution locale de Kubernetes.
+Minikube est un outil facilitant l’exécution locale de Kubernetes.
 Minikube exécute un cluster Kubernetes à nœud unique dans une machine virtuelle (VM) de votre ordinateur portable pour les utilisateurs qui souhaitent essayer Kubernetes ou le développer au quotidien.
 
 {{% /capture %}}
@@ -53,7 +53,7 @@ Suivez les étapes ci-dessous pour commencer et explorer Minikube.
 2. Vous pouvez maintenant interagir avec votre cluster à l'aide de kubectl.
    Pour plus d'informations, voir [Interagir avec votre cluster.](#interacting-with-your-cluster).
 
-    Créons un déploiement Kubernetes en utilisant une image existante nommée `echoserver`, qui est un serveur HTTP, et exposez-la sur le port 8080 à l'aide de `--port`.
+    Créons un déploiement Kubernetes en utilisant une image existante nommée `echoserver`, qui est un serveur HTTP, et exposez-la sur le port 8080 à l’aide de `--port`.
 
     ```shell
     kubectl create deployment hello-minikube --image=k8s.gcr.io/echoserver:1.10
@@ -107,7 +107,7 @@ Suivez les étapes ci-dessous pour commencer et explorer Minikube.
    minikube service hello-minikube --url
    ```
 
-6. Pour afficher les détails de votre cluster local, copiez et collez l'URL que vous avez obtenue en tant que sortie dans votre navigateur.
+6. Pour afficher les détails de votre cluster local, copiez et collez l’URL que vous avez obtenue en tant que sortie dans votre navigateur.
 
     Le résultat est similaire à ceci:
 
@@ -306,7 +306,7 @@ minikube start \
 #### Utiliser des images locales en réutilisant le démon Docker
 
 Lorsque vous utilisez une seule machine virtuelle pour Kubernetes, il est utile de réutiliser le démon Docker intégré de Minikube.
-La réutilisation du démon intégré signifie que vous n'avez pas besoin de créer un registre Docker sur votre ordinateur hôte et d'y insérer l'image.
+La réutilisation du démon intégré signifie que vous n’avez pas besoin de créer un registre Docker sur votre ordinateur hôte et d’y insérer l’image.
 Au lieu de cela, vous pouvez créer le même démon Docker que Minikube, ce qui accélère les expériences locales.
 
 {{< note >}}
@@ -327,7 +327,7 @@ docker ps
 ```
 
 {{< note >}}
-Sur Centos 7, Docker peut signaler l'erreur suivante:
+Sur Centos 7, Docker peut signaler l’erreur suivante:
 
 ```text
 Could not read CA certificate "/etc/docker/ca.pem": open /etc/docker/ca.pem: no such file or directory
@@ -433,7 +433,7 @@ Minikube supporte les [PersistentVolumes](/docs/concepts/storage/persistent-volu
 Ces volumes persistants sont mappés vers un répertoire à l'intérieur de la VM Minikube.
 
 La machine virtuelle Minikube démarre dans un fichier tmpfs, de sorte que la plupart des répertoires ne seront pas conservés lors des redémarrages avec (`minikube stop`).
-Toutefois, Minikube est configuré pour conserver les fichiers stockés dans les répertoires d'hôte suivants:
+Toutefois, Minikube est configuré pour conserver les fichiers stockés dans les répertoires d’hôte suivants:
 
 * `/data`
 * `/var/lib/minikube`
@@ -489,7 +489,7 @@ Minikube crée une machine virtuelle qui inclut Kubernetes et un démon Docker.
 Lorsque Kubernetes tente de planifier des conteneurs à l'aide de Docker, le démon Docker peut nécessiter un accès réseau externe pour extraire les conteneurs.
 
 Si vous êtes derrière un proxy HTTP, vous devrez peut-être fournir à Docker les paramètres de proxy.
-Pour ce faire, transmettez les variables d'environnement requises en tant qu'indicateurs lors de la création de `minikube start`.
+Pour ce faire, transmettez les variables d’environnement requises en tant qu’indicateurs lors de la création de `minikube start`.
 
 Par exemple:
 
@@ -522,8 +522,8 @@ Pour plus d'informations sur Minikube, voir la [proposition](https://git.k8s.io/
 * **Guide de développement**: Voir [CONTRIBUTING.md](https://git.k8s.io/minikube/CONTRIBUTING.md) pour avoir un aperçu de comment envoyer des pull requests.
 * **Construire Minikube**: Pour obtenir des instructions sur la création / test de Minikube à partir des sources, voir le [guide de build](https://git.k8s.io/minikube/docs/contributors/build_guide.md).
 * **Ajout d'une nouvelle dépendance**: Pour savoir comment ajouter une nouvelle dépendance à Minikube, voir la section [guide d'ajout de dépendances](https://git.k8s.io/minikube/docs/contributors/adding_a_dependency.md).
-* **Ajout d'un nouvel addon**: Pour savoir comment ajouter un nouvel addon pour Minikube, reportez-vous au [Ajout d'un addon](https://git.k8s.io/minikube/docs/contributors/adding_an_addon.md).
-* **MicroK8s**: Les utilisateurs de Linux qui souhaitent éviter d'exécuter une machine virtuelle peuvent envisager [MicroK8s](https://microk8s.io/).
+* **Ajout d'un nouvel addon**: Pour savoir comment ajouter un nouvel addon pour Minikube, reportez-vous au [Ajout d’un addon](https://git.k8s.io/minikube/docs/contributors/adding_an_addon.md).
+* **MicroK8s**: Les utilisateurs de Linux qui souhaitent éviter d’exécuter une machine virtuelle peuvent envisager [MicroK8s](https://microk8s.io/).
 
 ## Communauté
 

diff --git a/content/ja/docs/setup/learning-environment/minikube.md b/content/ja/docs/setup/learning-environment/minikube.md
@@ -31,9 +31,6 @@ Minikubeはローカル環境でKubernetesを簡単に実行するためのツ
 これはMinikubeの使い方の簡単なデモです。
 もしVMドライバを変更したい場合は、適切な `--driver=xxx` フラグを `minikube start` に設定してください。Minikubeは以下のドライバをサポートしています。
 
-* vmware ([installation du pilote](https://minikube.sigs.k8s.io/docs/reference/drivers/vmware/)) (VMware unified driver)
-* parallels ([installation du pilote](https://minikube.sigs.k8s.io/docs/reference/drivers/parallels/))
-
 * virtualbox
 * vmwarefusion
 * docker (EXPERIMENTAL)
@@ -94,27 +91,27 @@ curl $(minikube service hello-minikube --url)
 Hostname: hello-minikube-7c77b68cff-8wdzq
 
 Pod Information:
-  -no pod information available-
+	-no pod information available-
 
 Server values:
-  server_version=nginx: 1.13.3 - lua: 10008
+	server_version=nginx: 1.13.3 - lua: 10008
 
 Request Information:
-  client_address=172.17.0.1
-  method=GET
-  real path=/
-  query=
-  request_version=1.1
-  request_scheme=http
-  request_uri=http://192.168.99.100:8080/
+	client_address=172.17.0.1
+	method=GET
+	real path=/
+	query=
+	request_version=1.1
+	request_scheme=http
+	request_uri=http://192.168.99.100:8080/
 
 Request Headers:
-  accept=*/*
-  host=192.168.99.100:30674
-  user-agent=curl/7.47.0
+	accept=*/*
+	host=192.168.99.100:30674
+	user-agent=curl/7.47.0
 
 Request Body:
-  -no body in request-
+	-no body in request-
 ```
 
 ```shell

diff --git a/content/ja/docs/tasks/tools/install-minikube.md b/content/ja/docs/tasks/tools/install-minikube.md
@@ -71,9 +71,9 @@ kubectlがインストールされていることを確認してください。
 
 ハイパーバイザーがまだインストールされていない場合は、これらのいずれかをインストールしてください:
 
-* [KVM](https://www.linux-kvm.org/)、ただしQEMUも使っているもの
+• [KVM](https://www.linux-kvm.org/)、ただしQEMUも使っているもの
 
-* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 
 {{< note >}}
 minikubeは、VMではなくホストでKubernetesコンポーネントを実行する`--driver=none`オプションもサポートしています。
@@ -116,11 +116,11 @@ kubectlがインストールされていることを確認してください。
 
 ハイパーバイザーがまだインストールされていない場合は、これらのいずれかをインストールしてください:
 
-* [HyperKit](https://github.com/moby/hyperkit)
+• [HyperKit](https://github.com/moby/hyperkit)
 
-* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 
-* [VMware Fusion](https://www.vmware.com/products/fusion)
+• [VMware Fusion](https://www.vmware.com/products/fusion)
 
 ### Minikubeのインストール
 [Homebrew](https://brew.sh)を使うことでmacOSにMinikubeを簡単にインストールできます:
@@ -153,9 +153,9 @@ kubectlがインストールされていることを確認してください。
 
 ハイパーバイザーがまだインストールされていない場合は、これらのいずれかをインストールしてください:
 
-* [Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install)
+• [Hyper-V](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install)
 
-* [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
+• [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
 
 {{< note >}}
 Hyper-Vは、Windows 10 Enterprise、Windows 10 Professional、Windows 10 Educationの3つのバージョンのWindows 10で実行できます。

diff --git a/content/ko/docs/setup/learning-environment/minikube.md b/content/ko/docs/setup/learning-environment/minikube.md
@@ -68,24 +68,24 @@ Minikube는 다음과 같은 쿠버네티스의 기능을 제공한다.
     ```
 4. `hello-minikube` 파드가 이제 시작되었지만 노출된 서비스를 통해서 접근하기 전에 파드가 뜨기를 기다려야한다.
 
-  파드가 떠서 구동되고 있는지 확인한다.
-  ```shell
-  kubectl get pod
-  ```
-  출력에서 `STATUS`가 `ContainerCreating`으로 나타나는 경우, 파드는 아직 생성 중이다.
-  ```
-  NAME                              READY     STATUS              RESTARTS   AGE
-  hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
-  ```
-  출력에서 `STATUS`가 `Running`으로 나타나는 경우, 파드는 이제 떠서 기동 중이다.
-  ```
-  NAME                              READY     STATUS    RESTARTS   AGE
-  hello-minikube-3383150820-vctvh   1/1       Running   0          13s
-  ```
+	파드가 떠서 구동되고 있는지 확인한다.
+	```shell
+	kubectl get pod
+	```
+	출력에서 `STATUS`가 `ContainerCreating`으로 나타나는 경우, 파드는 아직 생성 중이다.
+	```
+	NAME                              READY     STATUS              RESTARTS   AGE
+	hello-minikube-3383150820-vctvh   0/1       ContainerCreating   0          3s
+	```
+	출력에서 `STATUS`가 `Running`으로 나타나는 경우, 파드는 이제 떠서 기동 중이다.
+	```
+	NAME                              READY     STATUS    RESTARTS   AGE
+	hello-minikube-3383150820-vctvh   1/1       Running   0          13s
+	```
 5. 서비스 상세를 보기 위해서 노출된 서비스의 URL을 얻는다.
-  ```shell
-  minikube service hello-minikube --url
-  ```
+	```shell
+	minikube service hello-minikube --url
+	```
 6. 로컬 클러스터의 상세를 보기위해서, 출력에서 얻은 URL을 브라우저에 복사해서 붙여 넣는다.
 
     출력은 다음과 비슷하다.
@@ -141,7 +141,7 @@ Minikube는 다음과 같은 쿠버네티스의 기능을 제공한다.
     Stopping "minikube"...
     "minikube" stopped.
     ```
-  보다 상세한 정보는 [클러스터 중지하기](#클러스터-중지하기)를 참조한다.
+	보다 상세한 정보는 [클러스터 중지하기](#클러스터-중지하기)를 참조한다.
 10. 로컬 Minikube 클러스터 삭제
     ```shell
     minikube delete
@@ -151,7 +151,7 @@ Minikube는 다음과 같은 쿠버네티스의 기능을 제공한다.
     Deleting "minikube" ...
     The "minikube" cluster has been deleted.
     ```
-  보다 상세한 정보는 [Deleting a cluster](#클러스터-삭제하기)를 참조한다.
+	보다 상세한 정보는 [Deleting a cluster](#클러스터-삭제하기)를 참조한다.
 
 ## 클러스터 관리하기