From a6887da923c7f93bab89bc081b7156b840d8d9b8 Mon Sep 17 00:00:00 2001 From: Ian Babrou Date: Mon, 30 Mar 2015 21:59:15 -0700 Subject: [PATCH] menu is on the right now --- docs/content/Design.md | 2 +- docs/content/Realtime.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/Design.md b/docs/content/Design.md index 1c70bc14bf4..aadc23e1b51 100644 --- a/docs/content/Design.md +++ b/docs/content/Design.md @@ -25,7 +25,7 @@ Druid is a good fit for products that require real-time data ingestion of a sing Druid is architected as a grouping of systems each with a distinct role and together they form a working system. The name comes from the Druid class in many role-playing games: it is a shape-shifter, capable of taking many different forms to fulfill various different roles in a group. -Each of the systems, or components, described below also has a dedicated page with more details. You can find the page in the menu on the left, or click the link in the component's description. +Each of the systems, or components, described below also has a dedicated page with more details. You can find the page in the menu on the right, or click the link in the component's description. The node types that currently exist are: diff --git a/docs/content/Realtime.md b/docs/content/Realtime.md index acfdaea265d..ef9f63a633b 100644 --- a/docs/content/Realtime.md +++ b/docs/content/Realtime.md @@ -21,7 +21,7 @@ The segment propagation diagram for real-time data ingestion can be seen below: ![Segment Propagation](../img/segmentPropagation.png "Segment Propagation") -You can read about the various components shown in this diagram under the Architecture section (see the menu on the left). Note that some of the names are now outdated. +You can read about the various components shown in this diagram under the Architecture section (see the menu on the right). Note that some of the names are now outdated. ### Firehose