Fix example safety caps table

Author: StephenBrown2

docs/docs/While You Wait For Gear/example-max-safety-chart.md

@@ -75,9 +75,9 @@ your data, customized watchfaces with your OpenAPS data, and integration with IF
 **The remaining variables can be left at their default values.**</br></br>
 
 *****************
-**Note:** for `BRIDGE_MAX_COUNT`: This value sets the number of BG values to pull from Share per update.  Each Dexcom BG value represent 5 minutes.  Nightscout defaults to `BRIDGE_MAX_COUNT=1`.  If you lose connectivity with your Dexcom transmitter, your Share app will automatically backfill data points when you regain connectivity.  Nightscount does not do this and you will have gaps in the data for when you were out of range.  More information [here](https://github.com/nightscout/cgm-remote-monitor#bridge-share2nightscout-bridge).
+**Note:** for BRIDGE_MAX_COUNT: This value sets the number of BG values to pull from Share per update.  Each Dexcom BG value represent 5 minutes.  Nightscout defaults to BRIDGE_MAX_COUNT=1.  If you lose connectivity with your Dexcom transmitter, your Share app will automatically backfill data points when you regain connectivity.  Nightscount does not do this and you will have gaps in the data for when you were out of range.  More information [here](https://github.com/nightscout/cgm-remote-monitor#bridge-share2nightscout-bridge).
 
-You can change the `BRIDGE_MAX_COUNT` value to pull more samples per query, which will backfill BRIDGE_MAX_COUNT values for you.  This change increases your data usage and may affect your Nightscout billing tier.   Setting BRIDGE_MAX_COUNT to 7 will update the previous 35 minutes of data and will keep OpenAPS up to date on your current BG trends.  If you frequently have larger data gaps and you use autotune, you may consider increasing this number more to backfill data more aggressively.
+You can change the BRIDGE_MAX_COUNT value to pull more samples per query, which will backfill BRIDGE_MAX_COUNT values for you.  This change increases your data usage and may affect your Nightscout billing tier.   Setting BRIDGE_MAX_COUNT to 7 will update the previous 35 minutes of data and will keep OpenAPS up to date on your current BG trends.  If you frequently have larger data gaps and you use autotune, you may consider increasing this number more to backfill data more aggressively.
 *****************
 
 * Click the purple `Deploy` button at the bottom of screen.
@@ -139,7 +139,7 @@ Your NIGHTSCOUT site is now all set-up.  Congrats!
 
 ## Nightscout Migrations
 
-### Switching from `API_SECRET` to token based authentication for your rig
+### Switching from API_SECRET to token based authentication for your rig
 
 You can secure your Nightscout and CGM data with [token based authentication](http://www.nightscout.info/wiki/welcome/website-features/0-9-features/authentication-roles).
 This requires Nightscout 0.9 (Grilled Cheese) and oref0 0.5.0 or later.

docs/docs/While You Wait For Gear/examples_safety_caps_in_play.png

@@ -138,7 +138,15 @@ You can also view this message in the Nightscout OpenAPS pill (which pops up a d
 
 #### A few examples:
 
-![Example safety cap image - see raw file in the same folder of docs if needs editing](examples_safety_caps_in_play.png)
+|     | Example 1 | Example 2 | Example 3 | Example 4 |
+| --- | --------- | --------- | --------- | --------- |
+| user's max basal safety setting (in pump) | 2.0 | 2.0 | 3.0 | 2.5 |
+| `max_daily_safety_multiplier` | 3 | 3 | 3 | 3 |
+| `current_basal_safety_multiplier` | 4 | 4 | 4 | 4 |
+| user's current basal rate | 1.0 | 0.4 | 1.2 | 0.7 |
+| user's highest programmed basal rate | 1.5 | 1.0 | 1.2 | 0.8 |
+| OpenAPS recommended temp basal rate | 3.0 | 1.8 | 2.4 | 2.6 |
+| Actual temp basal rate allowed | 2.0 | 1.6 | 2.4 | 2.4 |
 
 * In **Example 1**, the user's max basal safety setting is the constraining limit on the OpenAPS recommended temp basal rate.
 * In **Example 2**, 4x the user's current basal rate is the constraining limit on the OpenAPS recommended temp basal rate.