Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed typos in README.md #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed typos in README.md #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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()``.

Expand Down