Fix "Summary" block titles

Author: markerikson

docs/tutorials/essentials/part-1-overview-concepts.md

@@ -441,7 +441,7 @@ Here's what that data flow looks like visually:
 
 Redux does have a number of new terms and concepts to remember. As a reminder, here's what we just covered:
 
-:::Summary
+:::tip Summary
 
 - **Redux is a library for managing global application state**
   - Redux is typically used with the React-Redux library for integrating Redux and React together

docs/tutorials/essentials/part-2-app-structure.md

@@ -728,7 +728,7 @@ Now, any React components that call `useSelector` or `useDispatch` will be talki
 
 Even though the counter example app is pretty small, it showed all the key pieces of a React + Redux app working together. Here's what we covered:
 
-:::Summary
+:::tip Summary
 
 - **We can create a Redux store using the Redux Toolkit `configureStore` API**
   - `configureStore` accepts a `reducer` function as a named argument

docs/tutorials/essentials/part-3-data-flow.md

@@ -428,7 +428,7 @@ Notice that our `AddPostForm` component has some React `useState` hooks inside,
 
 Let's recap what you've learned in this section:
 
-:::Summary
+:::tip Summary
 
 - **Redux state is updated by "reducer functions"**:
   - Reducers always calculate a new state _immutably_, by copying existing state values and modifying the copies with the new data

docs/tutorials/essentials/part-4-using-data.md

@@ -819,7 +819,7 @@ It's actually starting to look more useful and interesting!
 
 We've covered a lot of information and concepts in this section. Let's recap the important things to remember:
 
-:::Summary
+:::tip Summary
 
 - **Any React component can use data from the Redux store as needed**
   - Any component can read any data that is in the Redux store

docs/tutorials/essentials/part-5-async-logic.md

@@ -784,7 +784,7 @@ Here's what our app looks like now that we're fetching data from that fake API:
 
 As a reminder, here's what we covered in this section:
 
-:::Summary
+:::tip Summary
 
 - **You can write reusable "selector" functions to encapsulate reading values from the Redux state**
   - Selectors are functions that get the Redux `state` as an argument, and return some data

docs/tutorials/essentials/part-6-performance-normalization.md

@@ -978,7 +978,7 @@ Congratulations, you've completed the Redux Essentials tutorial! Let's see what
 
 Here's what we covered in this section:
 
-:::Summary
+:::tip Summary
 
 - **Memoized selector functions can be used to optimize performance**
   - Redux Toolkit re-exports the `createSelector` function from Reselect, which generates memoized selectors

docs/tutorials/fundamentals/part-1-overview.md

@@ -307,7 +307,7 @@ That counter example was small, but it does show all the working pieces of a rea
 
 With that in mind, let's review what we've learned so far:
 
-:::Summary
+:::tip Summary
 
 - **Redux is a library for managing global application state**
   - Redux is typically used with the React-Redux library for integrating Redux and React together

docs/tutorials/fundamentals/part-2-concepts-data-flow.md

@@ -357,7 +357,7 @@ Here's what that data flow looks like visually:
 
 ## What You've Learned
 
-:::Summary
+:::tip Summary
 
 - **Redux's intent can be summarized in three principles**
   - Global app state is kept in a single store

docs/tutorials/fundamentals/part-3-state-actions-reducers.md

@@ -706,7 +706,7 @@ Here's the contents of our app so far:
   sandbox="allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts"
 ></iframe>
 
-:::Summary
+:::tip Summary
 
 - **Redux apps use plain JS objects, arrays, and primitives as the state values**
   - The root state value should be a plain JS object

docs/tutorials/fundamentals/part-4-store.md

@@ -606,7 +606,7 @@ Let's see how our example app looks now:
 
 And as a reminder, here's what we covered in this section:
 
-:::Summary
+:::tip Summary
 
 - **Redux apps always have a single store**
   - Stores are created with the Redux `createStore` API

docs/tutorials/fundamentals/part-5-ui-and-react.md

@@ -553,7 +553,7 @@ Let's see how the app looks now, including the components and sections we skippe
   sandbox="allow-modals allow-forms allow-popups allow-scripts allow-same-origin"
 ></iframe>
 
-:::Summary
+:::tip Summary
 
 - **Redux stores can be used with any UI layer**
   - UI code always subscribes to the store, gets the latest state, and redraws itself

docs/tutorials/fundamentals/part-6-async-logic.md

@@ -445,7 +445,7 @@ Here's what the current app looks like:
   sandbox="allow-modals allow-forms allow-popups allow-scripts allow-same-origin"
 ></iframe>
 
-:::Summary
+:::tip Summary
 
 - **Redux middleware were designed to enable writing logic that has side effects**
   - "Side effects" are code that changes state/behavior outside a function, like AJAX calls, modifying function arguments, or generating random values

docs/tutorials/fundamentals/part-7-standard-patterns.md

@@ -972,7 +972,7 @@ Here's how our app looks after it's been fully converted to use these patterns:
   sandbox="allow-modals allow-forms allow-popups allow-scripts allow-same-origin"
 ></iframe>
 
-:::Summary
+:::tip Summary
 
 - **Action creator functions encapsulate preparing action objects and thunks**
   - Action creators can accept arguments and contain setup logic, and return the final action object or thunk function

docs/tutorials/fundamentals/part-8-modern-redux.md

@@ -838,7 +838,7 @@ Let's take one final look at the completed todo application, including all the c
 
 And we'll do a final recap of the key points you learned in this section:
 
-:::Summary
+:::tip Summary
 
 - **Redux Toolkit (RTK) is the standard way to write Redux logic**
   - RTK includes APIs that simplify most Redux code