Fixed some documents (apache#794)

ivankelly · Sep 26, 2017 · c5d4f90 · c5d4f90
1 parent fea1b33
commit c5d4f90
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/site/_includes/explanations/install-package.md b/site/_includes/explanations/install-package.md
@@ -31,12 +31,12 @@ Once the tarball is downloaded, untar it and `cd` into the resulting directory:
 
 ```bash
 # Source release
-$ tar xvfz pulsar-{{ site.current_version }}-src.tar.gz
-$ cd pulsar-{{ site.current_version }}
+$ tar xvfz apache-pulsar-{{ site.current_version }}-src.tar.gz
+$ cd apache-pulsar-{{ site.current_version }}
 
 # Binary release
 $ tar xvfz apache-pulsar-{{ site.current_version }}-bin.tar.gz
-$ cd pulsar-{{ site.current_version }}
+$ cd apache-pulsar-{{ site.current_version }}
 ```
 
 ## What your package contains

diff --git a/site/_includes/explanations/service-discovery-setup.md b/site/_includes/explanations/service-discovery-setup.md
@@ -3,7 +3,7 @@
 You can also use your own service discovery system if you'd like. If you use your own system, there is just one requirement: when a client performs an HTTP request to an [endpoint](../../reference/Configuration) for a Pulsar {% popover cluster %}, such as `http://pulsar.us-west.example.com:8080`, the client needs to be redirected to *some* active broker in the desired cluster, whether via DNS, an HTTP or IP redirect, or some other means.
 
 {% include admonition.html type="success" title="Service discovery already provided by many scheduling systems" content="
-Many large-scale deployment systems, such as [Kubernetes](../../deployment/Kubernetes), have service discovery systems built in. If you're running Pulsar on such a system, you many not need to provide your own service discovery mechanism.
+Many large-scale deployment systems, such as [Kubernetes](../../deployment/Kubernetes), have service discovery systems built in. If you're running Pulsar on such a system, you may not need to provide your own service discovery mechanism.
 " %}
 
 ### Service discovery setup

diff --git a/site/docs/latest/deployment/Kubernetes.md b/site/docs/latest/deployment/Kubernetes.md
@@ -262,7 +262,7 @@ You can then access the dashboard in your web browser at [localhost:3000](http:/
 
 #### Pulsar dashboard
 
-While Grafana and Prometheus are used to provide graphs with historical data, [Pulsar dashboard](../../admin/Dashbaord) reports more detailed current data for individual {% popover topics %}.
+While Grafana and Prometheus are used to provide graphs with historical data, [Pulsar dashboard](../../admin/Dashboard) reports more detailed current data for individual {% popover topics %}.
 
 For example, you can have sortable tables showing all namespaces, topics, and broker stats, with details on the IP address for consumers, how long they've been connected, and much more.
 

diff --git a/site/docs/latest/deployment/Monitoring.md b/site/docs/latest/deployment/Monitoring.md
@@ -76,7 +76,7 @@ For that reason we only collect time series of metrics aggregated at the namespa
 
 ### Pulsar per-topic dashboard
 
-The per-topic dashboard instructions are available at [Dashboard](../Dashboard).
+The per-topic dashboard instructions are available at [Dashboard](../../admin/Dashboard).
 
 ### Grafana