From fba4ae428d483374ee952c4d346a1d64c650b6f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=BCrgen=20Gmach?= Date: Mon, 11 Nov 2019 11:35:40 +0100 Subject: [PATCH] Fix typo. --- docs/socketexample.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/socketexample.rst b/docs/socketexample.rst index e03dbab..d75f5a9 100644 --- a/docs/socketexample.rst +++ b/docs/socketexample.rst @@ -4,7 +4,7 @@ The Zope 3 Component Architecture (Socket Example) The component architecture provides an application framework that provides its functionality through loosely-connected components. A *component* can be any Python object and has a particular purpose associated with it. Thus, in a -component-based applications you have many small component in contrast to +component-based applications you have many small components in contrast to classical object-oriented development, where you have a few big objects. Components communicate via specific APIs, which are formally defined by