[#1081]: add clarifying comment why deleteStrategy is get during runtime

Signed-off-by: Florian Fendt <Florian.Fendt@bosch.io>

connectivity/service/src/main/java/org/eclipse/ditto/connectivity/service/config/ConnectionContextProvider.java

@@ -72,7 +72,7 @@ default CompletionStage<ConnectionContext> getConnectionContext(final Connection
      * @param connectionId the connection id
      * @param dittoHeaders the ditto headers
      * @param subscriber the subscriber that will receive {@link org.eclipse.ditto.base.model.signals.events.Event}s
-     * @return a future that succeeds or fails depends on whether registration was successful.
+     * @return a future that succeeds or fails depending on whether registration was successful.
      */
     CompletionStage<Void> registerForConnectivityConfigChanges(ConnectionId connectionId,
             DittoHeaders dittoHeaders, ActorRef subscriber);

internal/utils/persistent-actors/src/main/java/org/eclipse/ditto/internal/utils/persistentactors/AbstractShardedPersistenceActor.java

@@ -451,6 +451,8 @@ private ReceiveBuilder handleByDeletedStrategyReceiveBuilder() {
         final var deletedStrategy = (CommandStrategy<C, S, K, E>) getDeletedStrategy();
         return ReceiveBuilder.create()
                 .match(deletedStrategy.getMatchingClass(), deletedStrategy::isDefined,
+                        // get the current deletedStrategy during "matching time" to allow implementing classes
+                        // to update the strategy during runtime
                         command -> handleByStrategy(command, (CommandStrategy<C, S, K, E>) getDeletedStrategy()));
     }