diff --git a/docs/operations/metrics.md b/docs/operations/metrics.md
index b742fff795d..ecadf53c4cd 100644
--- a/docs/operations/metrics.md
+++ b/docs/operations/metrics.md
@@ -350,7 +350,8 @@ These metrics are for the Druid Coordinator and are reset each time the Coordina
 
 ### JVM
 
-These metrics are only available if the `JVMMonitor` module is included.
+These metrics are only available if the `JvmMonitor` module is included in `druid.monitoring.monitors`.
+For more information, see [Enabling Metrics](../configuration/index.md#enabling-metrics).
 
 |Metric|Description|Dimensions|Normal Value|
 |------|-----------|----------|------------|
diff --git a/docs/querying/lookups.md b/docs/querying/lookups.md
index d69f31619a5..ec82dc93933 100644
--- a/docs/querying/lookups.md
+++ b/docs/querying/lookups.md
@@ -79,7 +79,7 @@ In native queries, lookups can be queried with [dimension specs or extraction fu
 
 Query Execution
 ---------------
-When executing an aggregation query involving lookup functions (like the SQL [`LOOKUP` function](sql-scalar.md#string-functions),
+When executing an aggregation query involving lookup functions, like the SQL [`LOOKUP` function](sql-scalar.md#string-functions),
 Druid can decide to apply them while scanning and aggregating rows, or to apply them after aggregation is complete. It
 is more efficient to apply lookups after aggregation is complete, so Druid will do this if it can. Druid decides this
 by checking if the lookup is marked as "injective" or not. In general, you should set this property for any lookup that