adjustion some mentions of message factory to HTTP factory

Author: dbu

clients/includes/further-reading.inc

@@ -1,5 +1,5 @@
 * Use :doc:`plugins </plugins/introduction>` to customize the way HTTP requests are sent and
   responses processed by following redirects, adding Authentication or Cookie
   headers and more.
-* Learn how you can decouple your code from any PSR-7 implementation by using a
-  :ref:`message factory <message-factory>`.
+* Learn how you can decouple your code from any PSR-7 implementation by using
+  the :ref:`HTTP factories <message-factory>`.

httplug/library-developers.rst

@@ -63,7 +63,7 @@ Messages
 --------
 
 When you construct HTTP message objects in your library, you should not depend on a concrete PSR-7 message
-implementation. Instead, use the :ref:`PHP-HTTP message factory <message-factory>`.
+implementation. Instead, use the :doc:`HTTP factories <../message/message-factory>`.
 
 Discovery
 ---------

message.rst

@@ -12,4 +12,5 @@ This package contains various PSR-7 tools which might be useful in an HTTP workf
 * Various Stream encoding tools
 * Message decorators
 * Message factory implementations for Guzzle PSR-7, Diactoros and Slim Framework.
+* Stream and URI factory implementations for Guzzle PSR-7 and Diactoros
 * Cookie implementation

message/message-factory.rst

@@ -11,7 +11,7 @@ Rationale
 
 While it should be possible to use every PSR-7 aware HTTP client with any
 request, URI and stream implementation, instantiating objects explicitly would
-still  tie the code to a specific implementation. If each reusable library is
+still tie the code to a specific implementation. If each reusable library is
 tied to a specific message implementation, an application could end up
 installing several message implementations. The factories move instantiation
 out of the library code, further decoupling libraries from implementation.

spelling_word_list.txt

@@ -30,6 +30,7 @@ sublicense
 sync
 toolbar
 username
+versa
 whitelist
 wiki
 Wikipedia