nitpick: make run loop description consistent

Author: eflanagan0

guides/release/state-management/patterns-for-state.md

@@ -210,7 +210,7 @@ Once the data loads, it updates the state, and data flows downward like normal
 
 Background events are similar to data loading. Something is scheduled to happen
 in the background, like a `setTimeout` or `setInterval`, a callback scheduled in
-the [runloop][2], or connection is opened to something that communicates
+the [run loop][2], or connection is opened to something that communicates
 directly with the app, like a websocket or a web worker. When these events occur
 and update state, they trigger a rerender just like data loading.
 

guides/release/upgrading/editions.md

@@ -114,8 +114,8 @@ want to:
   object model.
 - **Curly component invocation**, eliminating the ambiguity in templates between
   values and DOM creation.
-- **The runloop**. App developers should never have to write code that interacts
-  with the Ember runloop, even in tests.
+- **The run loop**. App developers should never have to write code that interacts
+  with the Ember run loop, even in tests.
 - **Ember "inner HTML" components**, and the confusing JavaScript API used to
   configure a component’s root element, like `tagName`, `classNameBindings`,
   etc.