Move processor section

Author: andreasohlund

nservicebus/transactional-session/index.md

@@ -63,8 +63,6 @@ Disposing of the transactional session without committing will roll back any cha
 > [!NOTE]
 > The `Commit` operation may fail and throw an exception for reasons outlined in the [failure scenarios section](#failure-scenarios).
 
-partial: remote-processor
-
 ## Requirements
 
 The transactional session feature requires a supported persistence package to store outgoing messages. This feature is currently supported for the following persistence packages:
@@ -85,6 +83,8 @@ It's recommended to not mix the processing of control messages with business mes
 - More accurate metrics: Metrics like critical time and queue length will accurately represent the performance of the control message processing and not be skewed by business messages
 - Simplified management: Knowing that the endpoint only processes control messages makes it possible to always retry all failed messages related to the endpoint via tools like ServicePulse
 
+partial: remote-processor
+
 ## Transaction consistency
 
 To guarantee atomic consistency across database and message operations, the transactional session requires the [outbox](/nservicebus/outbox) to be enabled. This combination of features provides the strongest consistency guarantees and is, therefore, the recommended, safe-by-default configuration.