[feat][doc] add conceptual docs (bundle assignment/splitting/algorith…

…ms...) for broker load balancing

docs/concepts-broker-load-balancing-overview.md

@@ -17,7 +17,7 @@ Due to the unpredictable topic volume and physical distance among distributed br
 
 - When topics are redistributed to other brokers, the cluster ensures the topics are instantaneously available to clients. The topics continue to guarantee the system performance, such as persistence, [ordering](./concepts-messaging.md#ordering-guarantee), [deduplication](./concepts-messaging.md#message-deduplication), [subscription type](./concepts-messaging.md#subscription-types), etc.
 
-## Load balancing in Pulsar
+## Broker load balancing in Pulsar
 
 Because Pulsar uses a [segment-centric architecture](./concepts-architecture-overview.md) and separates the message serving and storage layer, it is designed to benefit load balancing. 
 

docs/concepts-messaging.md

@@ -521,7 +521,7 @@ A master consumer is picked for a non-partitioned topic or each partition of a p
 
 When the master consumer disconnects, all (non-acknowledged and subsequent) messages are delivered to the next consumer in line.
 
-::: note
+:::note
 
 In some cases, a partition may have an older active consumer processing messages while a newly switched over active consumer starts receiving new messages. This may lead to message duplication or out-of-order.