From 38d2e3dda5d73ba00d27b3bf38fc0d767c21743d Mon Sep 17 00:00:00 2001 From: Kurt Date: Tue, 2 Jul 2019 20:15:33 -0400 Subject: [PATCH] Correct usage of 'comprise' --- v2:-Documentation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/v2:-Documentation.md b/v2:-Documentation.md index 592d836..556e0d7 100644 --- a/v2:-Documentation.md +++ b/v2:-Documentation.md @@ -73,8 +73,8 @@ HTTP App Routes are not your traditional notion of routes (i.e. "GET /foo/bar" -> someFunc). Routes in Caddy 2 are much more powerful. They are given in an ordered list, and each route has three parts: match, apply, respond. All parts are optional. Match is the "if" -statement of each route. Each route takes a list of matcher sets. A matcher set is -comprised of matchers of various types. A matcher may be comprised of multiple values. +statement of each route. Each route takes a list of matcher sets. A matcher set +comprises matchers of various types. A matcher may comprise multiple values. The boolean logic of request matching goes like this: - Matcher sets are OR'ed (first matching matcher set is sufficient) @@ -629,4 +629,4 @@ performance over a cluster of load-balanced instances, since TLS sessions can al resumed no matter the load balancing. -FIN. \ No newline at end of file +FIN.