diff --git a/docs/content/DimensionSpecs.md b/docs/content/DimensionSpecs.md
index 6c29e53fb5a7..c94cf9154da6 100644
--- a/docs/content/DimensionSpecs.md
+++ b/docs/content/DimensionSpecs.md
@@ -320,10 +320,6 @@ The extension `druid-dim-rename-kafka8` enables reading from a kafka feed which
 
 Currently the historical node caches the key/value pairs from the kafka feed in an ephemeral memory mapped DB via MapDB.
 
-Current limitations:
-* All rename feeds must be known at server startup and are not dynamically configurable
-* The query issuer must know the name of the kafka topic
-
 #### Configuration
 The following options are used to define the behavior:
 
diff --git a/docs/content/Historical-Config.md b/docs/content/Historical-Config.md
index f719ea8cb211..0dc6d260de70 100644
--- a/docs/content/Historical-Config.md
+++ b/docs/content/Historical-Config.md
@@ -109,4 +109,3 @@ The following are settings used by the historical nodes when setting namespaces
 |--------|-----------|-------|
 |`druid.query.extraction.namespace.cache.type`|Specifies the type of caching to be used by the namespaces. May be one of [`offHeap`, `onHeap`, `cache`]. `offHeap` uses a temporary file for off-heap storage of the namespace. `onHeap` stores all cache on the heap. `cache` attempts to piggyback the setup for `druid.cache`|`onHeap`|
 |`druid.query.extraction.namespace.enabled`|Specifies that processing of namespaces is to be enabled. This should only be set to `true` on historical nodes and should be absent or false everywhere else.|`false`|
-|`druid.zk.paths.namespacePath`|The path to pull namespace updates from|`${druid.zk.paths.base}/namespaces`|
\ No newline at end of file
diff --git a/docs/content/ZooKeeper.md b/docs/content/ZooKeeper.md
index d1bdf9230dc0..e36fd28aafff 100644
--- a/docs/content/ZooKeeper.md
+++ b/docs/content/ZooKeeper.md
@@ -49,7 +49,7 @@ The indexing service also uses its own set of paths. These configs can be includ
 If `druid.zk.paths.base` and `druid.zk.paths.indexer.base` are both set, and none of the other `druid.zk.paths.*` or `druid.zk.paths.indexer.*` values are set, then the other properties will be evaluated relative to their respective `base`.
 For example, if `druid.zk.paths.base` is set to `/druid1` and `druid.zk.paths.indexer.base` is set to `/druid2` then `druid.zk.paths.announcementsPath` will default to `/druid1/announcements` while `druid.zk.paths.indexer.announcementsPath` will default to `/druid2/announcements`.
 
-The following path is used service discovery and are **not** affected by `druid.zk.paths.base` and **must** be specified separately.
+The following path is used when Curator is used for service discovery and is **not** affected by `druid.zk.paths.base` and **must** be specified separately.
 
 |Property|Description|Default|
 |--------|-----------|-------|