Better description on what happens during eventing rebalance

On rebalance page at https://docs.couchbase.com/server/current/learn/clusters-and-availability/rebalance.html, for eventing service rebalance, we state that,

When an Eventing Service node has been added or removed, rebalance causes vBucket processing ownership to be redistributed among available Eventing Service nodes. After rebalance, the service continues to process mutations: checkpoint information ensures that no mutations are lost

Some minor changes to the above text would make it more intuitive for users to understand. As in below

When an Eventing Service node has been added or removed, rebalance causes mutation (vBucket processing ownership) & timer event processing workload to be redistributed among available Eventing Service nodes. Both during & after rebalance, eventing service continues to process mutations: checkpoint information ensures that no mutations are lost during rebalance