minor corrections

Author: DanielGoldfarb

examples/panels.ipynb

@@ -639,9 +639,9 @@
     "| volume     | volume_width     | horizontal thickness of volume bars\n",
     "|        | volume_linewidth     | thickness of edge surrounding volume bar                                                                                 \n",
     "\n",
-    "We can override any one of the six keyowrds in the above table using kwarg **` update_width_config `**.  We pass this kwarg a `dict()` containing one or more of the six width configuration items listed above.  The exact value we pass in will be used instead of the value generated by the width adjuster algorithm.  But for those items that we do not specify, the algorithm's value will be used (possibly modified by `scale_width_adjustment`).  Note that values set by **`update_width_config`** are taken exactly, and are ***not*** affected by `scale_width_adjustment`.\n",
+    "We can override any one of the six keywords in the above table using kwarg **` update_width_config `**.  We pass this kwarg a `dict()` containing one or more of the six keywords listed above.  The exact value we pass in will be used instead of the value generated by the width adjuster algorithm.  But for those items that we do not specify, the algorithm's value will be used (possibly modified by `scale_width_adjustment`).  Note that values set by **`update_width_config`** are taken exactly, and are ***not*** affected by `scale_width_adjustment`.\n",
     "\n",
-    "**A note of warning** about the values in the width configuration.  These values can vary greatly depending upon the data, ***especially if the user sets*** ` show_nontrading=True ` which can cause very large changes to the width configuration values _if the data is not daily_ (for example if it is weekly, monthly, or intraday).\n",
+    "**A note of warning** about the values in the width configuration.  These values can vary greatly depending upon the data, ***especially if the user sets*** ` show_nontrading=True `, which can cause large changes to the width configuration values depending on the frequency (intraday, weekly, monthly, etc) of the data.\n",
     "\n",
     "To mitigate the possibility of setting the width configuration to values that may not make sense, **you can see** the generated width configuration values using kwarg **` 'return_width_config' `**.  Simply set this kwarg equal to an **empty `dict()`** and mplfinance will return the width configuration values in the dict.  \n",
     "\n",