Skip to content
This repository was archived by the owner on Apr 19, 2022. It is now read-only.

Fixed typos in Readme #1

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

Fixed typos in Readme #1

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 @@ -62,9 +62,9 @@ But don't worry, **you don't have to learn Exo's OOP all at once** _(or even at
The benefits to learning and using Exo when building WordPress web apps are:
- **Handle Greater Complexity** - Exo allows an application's complexity to grow to a significantly greater level than can be realistically managed using defacto-standard approaches to building WordPress sites.

- **Reduces Duplication in Themes** - Most WordPress themes developed for highly custom sites are littered with complex business logic that is often duplicated in many places. Intermediate use of Exo can reduce the complexity, and advanced use can all but eliminated it. _(For you new-to-WordPress MVC aficionados we are talking about Separation of Concerns here.)_
- **Reduces Duplication in Themes** - Most WordPress themes developed for highly custom sites are littered with complex business logic that is often duplicated in many places. Intermediate use of Exo can reduce the complexity, and advanced use can all but eliminate it. _(For you new-to-WordPress MVC aficionados we are talking about Separation of Concerns here.)_

- **Consistency** - WordPress is notoriously inconsistent in [it's APIs](http://codex.wordpress.org/WordPress_APIs) and a fundamental principle of Exo's API is rigid consistency, while being as WordPress-ish as possible.
- **Consistency** - WordPress is notoriously inconsistent in [its APIs](http://codex.wordpress.org/WordPress_APIs) and a fundamental principle of Exo's API is rigid consistency, while being as WordPress-ish as possible.

- **Reusability** - WordPress by it's very nature makes it possible to create reusable end-user components, known as plugins and themes, but WordPress' structure does not encourage development of components that are easily reusable by developers. Exo, by it's very nature, changes that. Development teams should be able to easily build reusable components they can leverage across many different projects. Further, if a lot of WordPress development teams choose to standardize on Exo then expect many reusable classes to emerge on Github.com.

Expand Down