This is an automated email from the ASF dual-hosted git repository.
ayegorov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/bookkeeper.git
The following commit(s) were added to refs/heads/master by this push:
new 7bb0bfc [WEBSITE] Staging website: images are not visible
7bb0bfc is described below
commit 7bb0bfcafbfb7cb2ee330707e082f27c3a8fd530
Author: Nicolò Boschi <[email protected]>
AuthorDate: Fri Mar 18 17:40:43 2022 +0100
[WEBSITE] Staging website: images are not visible
### Motivation
In the staging website image links are broken
### Changes
* Fixed the links with the correct syntax (I checked every `img` reference)
Reviewers: Andrey Yegorov <None>
This closes #3126 from nicoloboschi/website/fix-imgs
---
site3/website/docs/api/distributedlog-api.md | 4 ++--
site3/website/docs/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.10.0/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.10.0/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.11.1/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.11.1/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.12.1/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.12.1/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.13.0/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.13.0/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.14.4/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.14.4/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.5.1/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.5.1/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.6.2/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.6.2/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.7.3/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.7.3/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.8.2/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.8.2/deployment/dcos.md | 8 ++++----
.../versioned_docs/version-4.9.2/api/distributedlog-api.md | 4 ++--
site3/website/versioned_docs/version-4.9.2/deployment/dcos.md | 8 ++++----
22 files changed, 66 insertions(+), 66 deletions(-)
diff --git a/site3/website/docs/api/distributedlog-api.md
b/site3/website/docs/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/docs/api/distributedlog-api.md
+++ b/site3/website/docs/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/docs/deployment/dcos.md
b/site3/website/docs/deployment/dcos.md
index bc8ad5a..b745fa2 100644
--- a/site3/website/docs/deployment/dcos.md
+++ b/site3/website/docs/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.10.0/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.10.0/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.10.0/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.10.0/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.10.0/deployment/dcos.md
b/site3/website/versioned_docs/version-4.10.0/deployment/dcos.md
index 0ad257a..1bc2a41 100644
--- a/site3/website/versioned_docs/version-4.10.0/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.10.0/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.11.1/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.11.1/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.11.1/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.11.1/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.11.1/deployment/dcos.md
b/site3/website/versioned_docs/version-4.11.1/deployment/dcos.md
index d676e75..f16b468 100644
--- a/site3/website/versioned_docs/version-4.11.1/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.11.1/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.12.1/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.12.1/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.12.1/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.12.1/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.12.1/deployment/dcos.md
b/site3/website/versioned_docs/version-4.12.1/deployment/dcos.md
index 1994e53..11e0b2d 100644
--- a/site3/website/versioned_docs/version-4.12.1/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.12.1/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.13.0/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.13.0/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.13.0/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.13.0/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.13.0/deployment/dcos.md
b/site3/website/versioned_docs/version-4.13.0/deployment/dcos.md
index e609d70..a59685a 100644
--- a/site3/website/versioned_docs/version-4.13.0/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.13.0/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.14.4/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.14.4/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.14.4/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.14.4/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.14.4/deployment/dcos.md
b/site3/website/versioned_docs/version-4.14.4/deployment/dcos.md
index 6835c9c..fef262a 100644
--- a/site3/website/versioned_docs/version-4.14.4/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.14.4/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.5.1/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.5.1/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.5.1/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.5.1/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.5.1/deployment/dcos.md
b/site3/website/versioned_docs/version-4.5.1/deployment/dcos.md
index 2ac86e1..c15b31e 100644
--- a/site3/website/versioned_docs/version-4.5.1/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.5.1/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.6.2/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.6.2/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.6.2/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.6.2/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.6.2/deployment/dcos.md
b/site3/website/versioned_docs/version-4.6.2/deployment/dcos.md
index 92de2a5..dcfc51a 100644
--- a/site3/website/versioned_docs/version-4.6.2/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.6.2/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.7.3/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.7.3/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.7.3/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.7.3/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.7.3/deployment/dcos.md
b/site3/website/versioned_docs/version-4.7.3/deployment/dcos.md
index b230386..1229d60 100644
--- a/site3/website/versioned_docs/version-4.7.3/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.7.3/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.8.2/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.8.2/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.8.2/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.8.2/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.8.2/deployment/dcos.md
b/site3/website/versioned_docs/version-4.8.2/deployment/dcos.md
index a79f65a..fc98edd 100644
--- a/site3/website/versioned_docs/version-4.8.2/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.8.2/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
diff --git
a/site3/website/versioned_docs/version-4.9.2/api/distributedlog-api.md
b/site3/website/versioned_docs/version-4.9.2/api/distributedlog-api.md
index 20a016b..75e01f7 100644
--- a/site3/website/versioned_docs/version-4.9.2/api/distributedlog-api.md
+++ b/site3/website/versioned_docs/version-4.9.2/api/distributedlog-api.md
@@ -13,7 +13,7 @@ DistributedLog (DL) maintains sequences of records in
categories called *logs* (
The diagram below illustrates how the DistributedLog API works with BookKeeper:
-
+
## Logs
@@ -21,7 +21,7 @@ A *log* in DistributedLog is an ordered, immutable sequence
of *log records*.
The diagram below illustrates the anatomy of a log stream:
-
+
### Log records
diff --git a/site3/website/versioned_docs/version-4.9.2/deployment/dcos.md
b/site3/website/versioned_docs/version-4.9.2/deployment/dcos.md
index 2fd2c4d..a8b84f8 100644
--- a/site3/website/versioned_docs/version-4.9.2/deployment/dcos.md
+++ b/site3/website/versioned_docs/version-4.9.2/deployment/dcos.md
@@ -40,25 +40,25 @@ The bookie that is automatically started up uses the host
mode of the network an
To watch BookKeeper start up, click on the **Services** tab in the DC/OS [user
interface](https://docs.mesosphere.com/latest/gui/) and you should see the
`bookkeeper` package listed:
-
+
### Tasks
To see which tasks have started, click on the `bookkeeper` service and you'll
see an interface that looks like this;
-
+
## Scaling BookKeeper
Once the first bookie has started up, you can click on the **Scale** tab to
scale up your BookKeeper ensemble by adding more bookies (or scale down the
ensemble by removing bookies).
-
+
## ZooKeeper Exhibitor
ZooKeeper contains the information for all bookies in the ensemble. When
deployed on DC/OS, BookKeeper uses a ZooKeeper instance provided by DC/OS. You
can access a visual UI for ZooKeeper using
[Exhibitor](https://github.com/soabase/exhibitor/wiki), which is available at
[http://master.dcos/exhibitor](http://master.dcos/exhibitor).
-
+
You should see a listing of IP/host information for all bookies under the
`messaging/bookkeeper/ledgers/available` node.
