Merge pull request #110933 from erikadoyle/subprocessfork

Move subprocess forking to more apropos place

Author: PRMerger12

articles/service-fabric/service-fabric-concepts-partitioning.md

@@ -344,9 +344,6 @@ As we literally want to have one partition per letter, we can use 0 as the low k
 
 The entire source code of the sample is available on [GitHub](https://github.com/Azure-Samples/service-fabric-dotnet-getting-started/tree/classic/Services/AlphabetPartitions).
 
-## Reliable Services and Actor forking subprocesses
-Service Fabric doesn't support reliable services and subsequently reliable actors forking subprocesses. An example of why its not supported is [CodePackageActivationContext](https://docs.microsoft.com/dotnet/api/system.fabric.codepackageactivationcontext?view=azure-dotnet) can not be used to register an unsupported subprocess, and cancellation tokens are only sent to registered processes; resulting in all sorts of issues, such as upgrade failures, when subprocesses don't close after the parent process has received a cancellation token. 
-
 ## Next steps
 For information on Service Fabric concepts, see the following:
 

articles/service-fabric/service-fabric-hosting-model.md

@@ -164,6 +164,10 @@ In the activation of 'MultiTypeServicePackage' for the replica of partition **P1
 
 In the preceding example, you might think that if 'MyCodePackageA' registers both 'MyServiceTypeA' and 'MyServiceTypeB', and there is no 'MyCodePackageB', then there is no redundant *CodePackage* running. Although this is correct, this application model does not align with the Exclusive Process hosting model. If the goal is to put each replica in its own dedicated process, you do not need to register both *ServiceTypes* from same *CodePackage*. Instead, you simply put each *ServiceType* in its own *ServicePackage*.
 
+### Reliable Services and Actor forking subprocesses
+
+Service Fabric doesn't support reliable services and subsequently reliable actors forking subprocesses. An example of why its not supported is [CodePackageActivationContext](https://docs.microsoft.com/dotnet/api/system.fabric.codepackageactivationcontext?view=azure-dotnet) can not be used to register an unsupported subprocess, and cancellation tokens are only sent to registered processes; resulting in all sorts of issues, such as upgrade failures, when subprocesses don't close after the parent process has received a cancellation token.
+
 ## Next steps
 [Package an application][a4] and get it ready to deploy.