Small changes to doc

Process Running (PR) alert conditions are being migrated to use NRQL (Willamette pipeline). This move will mean that they can no longer tell if a process failed to start when a host is spun up. I have tried to remove all references to that sort of behavior, since PR conditions will change to being more "Process NO LONGER running."

I feel like these changes will not need to be applied until we move the PR condition types over to Willamette (happening soon, but has not happened yet). On the other hand, these don't feel like breaking changes to the document, so could be published immediately without any impact (I think).

Please do send me a DM in Slack (@shenry) if you have any questions about these changes.

src/content/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/alert-infrastructure-processes.mdx

@@ -14,7 +14,7 @@ redirects:
 Use New Relic infrastructure's **Process running** [alert condition](/docs/infrastructure/new-relic-infrastructure/configuration/infrastructure-alerts-add-edit-or-view-host-alert-information) to be notified when a set of processes on your [filtered hosts](/docs/infrastructure/new-relic-infrastructure/filter-group/filter-sets-organize-your-infrastructure-hosts) stop running for a configurable number of minutes. This is useful, for example, when:
 
 * Any of the processes on the hosts stop reporting
-* A process you expected to start on a host (such as a new program) is not actually running
+* A process is running too many instances on one host
 
 This feature's flexibility allows you to easily filter what hosts and processes to monitor and when to notify selected individuals or teams. In addition, the email notification includes links to help you quickly troubleshoot the situation.
 
@@ -67,15 +67,6 @@ By applying filters to the hosts and processes that are important to your busine
     **Solution:** Use the **At least one process is running** threshold.
   </Collapser>
 
-  <Collapser
-    id="default-successful"
-    title="Validate that services started successfully"
-  >
-    **Problem:** When provisioning new hosts, you want to open a violation if a required service fails to successfully start up.
-
-    **Solution:** Use the **No processes are running** (default) threshold.
-  </Collapser>
-
   <Collapser
     id="multiple-runaway"
     title="Watch for runaway processes or configuration problems"