From 18b706d4fb83490168cb9d6df422071c0739e189 Mon Sep 17 00:00:00 2001 From: memoryruins Date: Fri, 6 Apr 2018 19:44:52 -0400 Subject: [PATCH] Guide: tweak to websocket and testing. --- guide/src/qs_8.md | 2 +- guide/src/qs_9.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/guide/src/qs_8.md b/guide/src/qs_8.md index 358d72ad0..f80fb8eb3 100644 --- a/guide/src/qs_8.md +++ b/guide/src/qs_8.md @@ -133,7 +133,7 @@ the websocket server and returns ws reader and writer objects. *TestServer* also provides an `execute()` method, which runs future objects to completion and returns result of the future computation. -The following example shows how to test a server websocket handler: +The following example demonstrates how to test a websocket handler: ```rust # extern crate actix; diff --git a/guide/src/qs_9.md b/guide/src/qs_9.md index b7fdc840a..e0d71f12b 100644 --- a/guide/src/qs_9.md +++ b/guide/src/qs_9.md @@ -6,7 +6,7 @@ a [*ws::WsStream*](../actix_web/ws/struct.WsStream.html) and then use stream combinators to handle actual messages, but it is simpler to handle websocket communications with an http actor. -The following is example of a simple websocket echo server: +The following is an example of a simple websocket echo server: ```rust # extern crate actix;