diff --git a/Notify_slack.md b/Notify_slack.md
index 91c2333..f118282 100644
--- a/Notify_slack.md
+++ b/Notify_slack.md
@@ -17,11 +17,11 @@ First off, Slack notifications require an *incoming-webhook* it can connect to.
 Regardless of what option you choose (above), both will result in giving you a webhook URL that looks something like this:<br/>
 ```https://hooks.slack.com/services/T1JJ3T3L2/A1BRTD4JD/TIiajkdnlazkcOXrIdevi7F```
 
-**Note:** Apprise supports this URL _as-is_ (_as of v0.7.7_); you no longer need to parse the URL any further.  However there is slightly less overhead (internally) if you do.
-
 This URL effectively equates to:<br/>
 ```https://hooks.slack.com/services/{tokenA}/{tokenB}/{tokenC}```
 
+**Note:** Apprise supports this URL _as-is_ (_as of v0.7.7_); you no longer need to parse the URL any further.  However there is slightly less overhead (internally) if you do.
+
 If you want to convert this to an Apprise URL, do the following:
 The last part of the URL you're given make up the 3 tokens you need to send notifications with  It's very important to pay attention.  In the above example the tokens are as follows:
 1. **TokenA** is ```T1JJ3T3L2```
@@ -31,7 +31,7 @@ The last part of the URL you're given make up the 3 tokens you need to send noti
 ### Syntax
 Valid syntaxes are as follows:
 * **slack**://**{tokenA}**/**{tokenB}**/**{tokenC}**
-* https://hooks.slack.com/services/**{tokenA}**/**{tokenB}**/**{tokenC}**
+* `https://hooks.slack.com/services/{tokenA}/{tokenB}/{tokenC}`
 
 Now if you're using the legacy webhook method (and not going through the App), you're granted a bit more freedom.  As a result, the following URLs will also work for you through Apprise:
 * **slack**://**{tokenA}**/**{tokenB}**/**{tokenC}**/**#{channel}**