From 83c85b3e45352b888567758b84a945e96c61b352 Mon Sep 17 00:00:00 2001 From: Document Doctor Date: Sat, 12 Jan 2019 01:53:41 -0500 Subject: [PATCH] Fixed typos in README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 98b2d5f..8abee40 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ templates to be used on both client and server. Google Closure Templates does not provide a clear set of standards for organizing and structuring your project. For example it provides little -guidance on managing namepsaces, shared resource, file naming conventions, +guidance on managing namespaces, shared resource, file naming conventions, caching and methods of integrating with existing tools. Silken wraps Google Closure Templates in a nice consumable form. @@ -604,7 +604,7 @@ import com.papercut.silken.Config; Config config = (Config) getServletContext().getAttribute("silken.config"); config.setLocaleResolver(new MyLocaleResolver()); ``` -A logical place to perform this initalization would be in a startup servlet's +A logical place to perform this initialization would be in a startup servlet's init method. It is also possible to access the ``Config`` class using the convenience method: ``SilkenServlet.getConfig()``.