Link fix (#16596)

* Link fix * Update docs/operations/auth.md Co-authored-by: Andreas Maechler <amaechler@gmail.com> --------- Co-authored-by: Andreas Maechler <amaechler@gmail.com>
apache · Jun 14, 2024 · aec1d5d · aec1d5d
1 parent eb842d3
commit aec1d5d
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/docs/operations/auth.md b/docs/operations/auth.md
@@ -54,7 +54,11 @@ Druid includes two built-in Authenticators, one of which is used for the default
 
 ### AllowAll authenticator
 
-This built-in Authenticator authenticates all requests, and always directs them to an Authorizer named "allowAll". It is not intended to be used for anything other than the default unsecured configuration.
+This built-in Authenticator authenticates all requests, and always directs them to an Authorizer named `allowAll`. It's not intended to be used for anything other than the default unsecured configuration.
+
+```properties
+druid.auth.authorizer.allowAll.type=allowAll
+```
 
 ### Anonymous authenticator
 

diff --git a/docs/operations/basic-cluster-tuning.md b/docs/operations/basic-cluster-tuning.md
@@ -91,7 +91,7 @@ Tuning the cluster so that each Historical can accept 50 queries and 10 non-quer
 #### Segment Cache Size
 
 For better query performance, do not allocate segment data to a Historical in excess of the system free memory. The Historical uses free system memory to cache segments.
-For more detail, see [Loading and serving segments from cache](../design/historical/#loading-and-serving-segments-from-cache)
+For more detail, see [Loading and serving segments from cache](../design/historical.md#loading-and-serving-segments-from-cache).
 
 Druid uses the `druid.segmentCache.locations` to calculate the total segment data size assigned to a Historical. For rare use cases, you can override this behavior with `druid.server.maxSize` property.