From 033b2b46393ee8f1c4763d532bc777ed48c72a93 Mon Sep 17 00:00:00 2001 From: "Gerasimos (Makis) Maropoulos" Date: Mon, 12 Aug 2019 12:04:08 +0300 Subject: [PATCH] minor misspell --- Routing-subdomains.md | 2 +- View.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Routing-subdomains.md b/Routing-subdomains.md index c7efc6e..9757abf 100644 --- a/Routing-subdomains.md +++ b/Routing-subdomains.md @@ -1,4 +1,4 @@ -Iris has the simplest known form for subdomains registration to a single application. Of course you can always use nginx or caddy for managment in production. +Iris has the simplest known form for subdomains registration to a single application. Of course you can always use nginx or caddy for management in production. Subdomains are separated into two categories: **static** and **dynamic/wildcard**. diff --git a/View.md b/View.md index 94451e8..1b0e8fe 100644 --- a/View.md +++ b/View.md @@ -1,6 +1,6 @@ Iris offers support for **6 template parsers out of the box** through its universal [View Engine](https://godoc.org/github.com/kataras/iris/view#Engine). Of course developers can still use various go template parsers as the `Context.ResponseWriter()` completes the `http.ResponseWriter` and `io.Writer`. -Iris puts some common rules and features that their original parsers don't support by default. For example we have support for `yield`, `render`, `render_r`, `current`, `urlpath` template funcs and `Layouts` and `binding` accross middlewares and **embedded template files** for all Engines. +Iris puts some common rules and features that their original parsers don't support by default. For example we have support for `yield`, `render`, `render_r`, `current`, `urlpath` template funcs and `Layouts` and `binding` across middlewares and **embedded template files** for all Engines. To use unique features of a template engine you have to learn the characteristics and the syntax by reading its documentation (click the links below). Choose what fits your app's needs the most.