[#1191] BIND9 => BIND 9

diff --git a/doc/sphinx/arm/stork.rst b/doc/sphinx/arm/stork.rst
index c8b82cf6a9c71df717d3675f0c08a6aacc3ac047..58a642ede96c9d7dde3e39b38a3a4b50a24e0902 100644 (file)
--- a/doc/sphinx/arm/stork.rst
+++ b/doc/sphinx/arm/stork.rst
@@ -7,7 +7,7 @@ Monitoring Kea with Stork
 It is usually desired to monitor running Kea services. Kea exposes many sources of informations:
 configuration files, API, statistics, logs, open database content and more. It may be sometimes
 overwhelming to keep up. ISC started the Stork project to address this problem for both Kea
-and BIND9. Stork can address a variety of scenarios:
+and BIND 9. Stork can address a variety of scenarios:
 
 - you can use Stork as a dashboard. It provides you with an insight into what exactly is going
   on with your servers. In particular, it can provide up to date details regarding pool
@@ -37,13 +37,13 @@ monthly release. Please check back frequently.
 Kea statistics in Grafana
 =========================
 
-The ISC Stork project provides an agent, that can be deployed along side Kea and BIND9. It will
+The ISC Stork project provides an agent, that can be deployed along side Kea and BIND 9. It will
 expose Kea statistics in a format that's acceptable by Prometheus.
 One of the major benefits of Prometheus is that it turns repeated one time observation into time series,
 which lets you monitor how certain behaviors change over time. It is easy to use other tools
 to visualize data available in Prometheus. The most common approach is to use
 Grafana to provide visual dashboards. The Stork project provides dashboard
-definitions for Kea and BIND9 that can be imported into Grafana very easily.
+definitions for Kea and BIND 9 that can be imported into Grafana very easily.
 
 You can learn more about Prometheus and Grafana on their websites: `Prometheus homepage <https://prometheus.io/>`_
 and `Grafana homepage <https://grafana.com/>`_.