From 0e1f3952b2e7adc10c2bccd764ca355e36746af5 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Tue, 26 Mar 2019 21:44:38 -0400 Subject: [PATCH] Updated Notify_gitter (markdown) --- Notify_gitter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Notify_gitter.md b/Notify_gitter.md index b557c55..33f2704 100644 --- a/Notify_gitter.md +++ b/Notify_gitter.md @@ -13,7 +13,7 @@ From here, you just need to get your Gitter **Personal Access Token** which is a The last thing you need to know about this is you need to have already joined the channel you wish to send notifications to. The **Personal Access Token** represents you, so even if you join a channel and close out of your web browser, you're still actually a part of that channel (until you log back in and leave the channel). -Channels identify themselves as **name**/community; you only need to focus on the name. So if the channel was **apprise**/community, the channel name can be assumed to be **apprise** when using this script. +Channels identify themselves as **name**/community; you only need to focus on the name. So if the channel was [**apprise**/community](https://gitter.im/apprise-notifications/community), the channel name can be assumed to be **apprise** when using this script. ### Syntax Valid syntaxes are as follows: * **gitter**://**{token}**/**{room}**/