diff --git a/site/building.md b/site/building.md
index 1cc4ba2d1..2073bbbc2 100644
--- a/site/building.md
+++ b/site/building.md
@@ -36,7 +36,7 @@ Similarly the frontent client tests can be run via:
make client-test
->**Note:** The tools from `make deps` depend on a local install of
+> **Note:** The tools from `make deps` depend on a local install of
[Go](https://golang.org).
## Debugging
diff --git a/site/plugins.md b/site/plugins.md
index a8a03191b..c072a9f76 100644
--- a/site/plugins.md
+++ b/site/plugins.md
@@ -34,13 +34,13 @@ Official Weave Scope plugins can be found at [Weaveworks Plugins](https://github
* Number of HTTP requests per seconds.
* Number of HTTP responses code per second (per code).
->**Note:** The HTTP Statistics plugin requires a [recent kernel version with ebpf support](https://github.com/iovisor/bcc/blob/master/INSTALL.md#kernel-configuration) and it will not compile on [dlite](https://github.com/nlf/dlite) or on boot2docker hosts.
+> **Note:** The HTTP Statistics plugin requires a [recent kernel version with ebpf support](https://github.com/iovisor/bcc/blob/master/INSTALL.md#kernel-configuration) and it will not compile on [dlite](https://github.com/nlf/dlite) or on boot2docker hosts.
* [Traffic Control](https://github.com/weaveworks-plugins/scope-traffic-control): This plugin allows you to modify latency and packet loss for a specific container via controls from the container's detailed view in the Scope user interface.
* [Volume Count](https://github.com/weaveworks-plugins/scope-volume-count): This plugin (written in Python) requests the number of mounted volumes for each container, and provides a container-level count.
->**Note:**Installed and running plugins are shown in the list of `PLUGINS` in the bottom right of the Scope UI.
+> **Note:**Installed and running plugins are shown in the list of `PLUGINS` in the bottom right of the Scope UI.
## How Plugins Communicate with Scope
@@ -88,7 +88,7 @@ For example:
}
```
->**Note:** The `Plugins` section includes exactly one plugin description that displays in the UI. The other plugin fields are:
+> **Note:** The `Plugins` section includes exactly one plugin description that displays in the UI. The other plugin fields are:
* `id` - checks for duplicate plugins. It is required.
* `label` - a human readable label displayed in the UI. It is required.