homelab/traefik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix typos in documentation

Browse source
This commit is contained in:
Michael 2019-05-17 11:32:05 +00:00 • committed by Traefiker Bot
parent f6df556eb0
commit 97ec764db7
8 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/content/routing/overview.md
View file

@ -3,7 +3,7 @@
What's Happening to the Requests?
{: .subtitle }
Let's zoom on Traefik's architecture and talk about the components that enable the routes to be created.
Let's zoom in on Traefik's architecture and talk about the components that enable the routes to be created.
First, when you start Traefik, you define [entrypoints](../entrypoints) (in their most basic forms, they are port numbers).
Then, connected to these entrypoints, [routers](../routers) analyze the incoming requests to see if they match a set of [rules](../routers#rule).

4
docs/content/routing/routers/index.md
View file

@ -51,7 +51,7 @@ In the process, routers may use pieces of [middleware](../../middlewares/overvie
### EntryPoints
If not specified, HTTP routers will accept requests from all defined entrypoints.
If you want to limit the router scope to a set of entrypoint, set the entrypoints option.
If you want to limit the router scope to a set of entrypoints, set the entrypoints option.
??? example "Listens to Every EntryPoint"
@ -92,7 +92,7 @@ If you want to limit the router scope to a set of entrypoint, set the entrypoint
### Rule
Rules are a set of matchers that determine if a particular request matches specific criteria.
If the rule is verified, then the router becomes active and calls middlewares, then forward the request to the service.
If the rule is verified, the router becomes active, calls middlewares, and then forwards the request to the service.
??? example "Host is traefik.io"