Edited wiki page AdaptorsInRelationToConnectors through web user interface.
diff --git a/AdaptorsInRelationToConnectors.wiki b/AdaptorsInRelationToConnectors.wiki
index 1979569..bd6cdd4 100644
--- a/AdaptorsInRelationToConnectors.wiki
+++ b/AdaptorsInRelationToConnectors.wiki
@@ -25,7 +25,7 @@
= The Lister/Retriever Model =
-The lister/retriever architecture of adaptors provides many advantages over using content feeds when you can randomly access content: simplicity, scalability, self-healing, stateless, transparent operation (easy monitoring and debugging), and it reuses existing infrastructure.
+The lister/retriever architecture of adaptors provides many advantages over using content feeds when you can randomly access content: simplicity, scalability, self-healing, statelessness, transparent operation (easy monitoring and debugging), and it reuses existing infrastructure.
The original expectation was that adaptors would have a slight performance loss when using only a single GSA. Since adaptors have the ability to scale to multiple GSAs, it was thought to likely be worth the performance penalty in the single-box setup. However, testing revealed that adaptors can actually be faster than connectors when the repository is not the bottleneck. For a file system repository containing no documents requiring text conversion and where latency could have had an impact, the adaptor performed 20% better than the corresponding connector. This in no way means there will always be a performance gain, but instead merely that it is possible and has happened.
