Fossil SCM
[Grammar] chat.md changes.
Commit
0c3aa7553bb8c35bed6133ad675a871c06a58f731769a8088b327714eea00688
Parent
35c515e7e82ee87…
1 file changed
+2
-2
+2
-2
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -155,11 +155,11 @@ | ||
| 155 | 155 | Substitute the appropriate project URL, robot account |
| 156 | 156 | name and password, message text and file attachment, of course. |
| 157 | 157 | |
| 158 | 158 | ### <a id="chat-robot"></a> Chat Messages For Timeline Events |
| 159 | 159 | |
| 160 | -If the [chat-timeline-user setting](/help?cmd=chat-timeline-user) is not a | |
| 160 | +If the [chat-timeline-user setting](/help?cmd=chat-timeline-user) is not an | |
| 161 | 161 | empty string, then any change to the repository that would normally result |
| 162 | 162 | in a new timeline entry is announced in the chatroom. The announcement |
| 163 | 163 | appears to come from a user whose name is given by the chat-timeline-user |
| 164 | 164 | setting. |
| 165 | 165 | |
| @@ -193,11 +193,11 @@ | ||
| 193 | 193 | * [/chat-delete](/help?name=/chat-delete) → |
| 194 | 194 | Deletes a chat message. |
| 195 | 195 | |
| 196 | 196 | Fossil chat uses the venerable "hanging GET" or |
| 197 | 197 | "[long polling](wikipedia:/wiki/Push_technology#Long_polling)" |
| 198 | -technique to recieve asynchronous notification of new messages. | |
| 198 | +technique to receive asynchronous notification of new messages. | |
| 199 | 199 | This is done because long polling works well with CGI and SCGI, |
| 200 | 200 | which are the usual mechanisms for setting up a Fossil server. |
| 201 | 201 | More advanced notification techniques such as |
| 202 | 202 | [Server-sent events](wikipedia:/wiki/Server-sent_events) and especially |
| 203 | 203 | [WebSockets](wikipedia:/wiki/WebSocket) might seem more appropriate for |
| 204 | 204 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -155,11 +155,11 @@ | |
| 155 | Substitute the appropriate project URL, robot account |
| 156 | name and password, message text and file attachment, of course. |
| 157 | |
| 158 | ### <a id="chat-robot"></a> Chat Messages For Timeline Events |
| 159 | |
| 160 | If the [chat-timeline-user setting](/help?cmd=chat-timeline-user) is not a |
| 161 | empty string, then any change to the repository that would normally result |
| 162 | in a new timeline entry is announced in the chatroom. The announcement |
| 163 | appears to come from a user whose name is given by the chat-timeline-user |
| 164 | setting. |
| 165 | |
| @@ -193,11 +193,11 @@ | |
| 193 | * [/chat-delete](/help?name=/chat-delete) → |
| 194 | Deletes a chat message. |
| 195 | |
| 196 | Fossil chat uses the venerable "hanging GET" or |
| 197 | "[long polling](wikipedia:/wiki/Push_technology#Long_polling)" |
| 198 | technique to recieve asynchronous notification of new messages. |
| 199 | This is done because long polling works well with CGI and SCGI, |
| 200 | which are the usual mechanisms for setting up a Fossil server. |
| 201 | More advanced notification techniques such as |
| 202 | [Server-sent events](wikipedia:/wiki/Server-sent_events) and especially |
| 203 | [WebSockets](wikipedia:/wiki/WebSocket) might seem more appropriate for |
| 204 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -155,11 +155,11 @@ | |
| 155 | Substitute the appropriate project URL, robot account |
| 156 | name and password, message text and file attachment, of course. |
| 157 | |
| 158 | ### <a id="chat-robot"></a> Chat Messages For Timeline Events |
| 159 | |
| 160 | If the [chat-timeline-user setting](/help?cmd=chat-timeline-user) is not an |
| 161 | empty string, then any change to the repository that would normally result |
| 162 | in a new timeline entry is announced in the chatroom. The announcement |
| 163 | appears to come from a user whose name is given by the chat-timeline-user |
| 164 | setting. |
| 165 | |
| @@ -193,11 +193,11 @@ | |
| 193 | * [/chat-delete](/help?name=/chat-delete) → |
| 194 | Deletes a chat message. |
| 195 | |
| 196 | Fossil chat uses the venerable "hanging GET" or |
| 197 | "[long polling](wikipedia:/wiki/Push_technology#Long_polling)" |
| 198 | technique to receive asynchronous notification of new messages. |
| 199 | This is done because long polling works well with CGI and SCGI, |
| 200 | which are the usual mechanisms for setting up a Fossil server. |
| 201 | More advanced notification techniques such as |
| 202 | [Server-sent events](wikipedia:/wiki/Server-sent_events) and especially |
| 203 | [WebSockets](wikipedia:/wiki/WebSocket) might seem more appropriate for |
| 204 |