Testing action updates

Author: keithort

.github/workflows/action.yml

@@ -11,5 +11,7 @@ jobs:
  - uses: actions/checkout@master
  - uses: gaurav-nelson/github-action-markdown-link-check@v1
  with:
+ config-file: 'mlc_config.json'
  use-quiet-mode: 'yes'
- use-verbose-mode: 'yes'
+ use-verbose-mode: 'yes'
+ 

.github/workflows/mlc_config.json

@@ -0,0 +1,10 @@
+{
+ "aliveStatusCodes": [
+ 0,
+ 200,
+ 429
+ ],
+ "fallbackRetryDelay": "30s",
+ "retryCount": 2,
+ "timeout": "5s"
+}

redux-architecture.md

@@ -191,11 +191,7 @@
  https://blog.shakacode.com/a-year-of-development-with-redux-part-i-a5791e124a7d 
  https://blog.shakacode.com/a-year-of-development-with-redux-part-ii-3035ff0b1781 
  Some quick tips for working with Redux, structuring data, and encapsulation of components
- 
-- **Avoiding False Cause** 
- http://duplo.tech/avoiding-false-cause/ 
- Some high-level general thoughts on cargo-culting, dogma, and best practices, followed by some specific examples of problematic Redux code (unclear reducer state shape, managing "editing" mode data, applying arbitrary value updates)
- 
+
 - **Isn't our code just the BEST** 
  https://medium.com/bumpers/isnt-our-code-just-the-best-f028a78f33a9 
  A quirkily-written look at how a dev team rewrote their project using React and Redux, including examples of project structure, component usage, and data normalization