james/fembooru
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed some spelling typos.

Browse Source
This commit is contained in:
jgen 2013-11-28 00:34:31 -05:00
parent a5ea9ed743
commit 13ea386b0e
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
index.php
View File

@ -3,7 +3,7 @@
* \mainpage Shimmie2 / SCore Documentation * \mainpage Shimmie2 / SCore Documentation
* *
* SCore is a framework designed for writing flexible, extendable applications. * SCore is a framework designed for writing flexible, extendable applications.
* Whereas most PHP apps are built monolithicly, score's event-based nature * Whereas most PHP apps are built monolithically, score's event-based nature
* allows parts to be mixed and matched. For instance, the most famous * allows parts to be mixed and matched. For instance, the most famous
* collection of score extensions is the Shimmie image board, which includes * collection of score extensions is the Shimmie image board, which includes
* user management, a wiki, a private messaging system, etc. But one could * user management, a wiki, a private messaging system, etc. But one could
@ -14,8 +14,8 @@
* *
* Dijkstra will kill me for personifying my architecture, but I can't think * Dijkstra will kill me for personifying my architecture, but I can't think
* of a better way without going into all the little details. * of a better way without going into all the little details.
* There are a bunch of Extension subclasses, they talk to eachother by sending * There are a bunch of Extension subclasses, they talk to each other by sending
* and recieving Event subclasses. The primary driver for each conversation is the * and receiving Event subclasses. The primary driver for each conversation is the
* initial PageRequestEvent. If an Extension wants to display something to the * initial PageRequestEvent. If an Extension wants to display something to the
* user, it adds a block to the Page data store. Once the conversation is over, the Page is passed to the * user, it adds a block to the Page data store. Once the conversation is over, the Page is passed to the
* current theme's Layout class which will tidy up the data and present it to * current theme's Layout class which will tidy up the data and present it to