summaryrefslogtreecommitdiff
path: root/demos/quickstart/protected/pages/Fundamentals
diff options
context:
space:
mode:
authorxue <>2005-12-28 14:05:40 +0000
committerxue <>2005-12-28 14:05:40 +0000
commitd109f8356d1dd2c66f66d316ee46a51043731206 (patch)
tree496db9a84db565856f44e85ad583700930ba9e03 /demos/quickstart/protected/pages/Fundamentals
parentc3bdc43f1b03cbea1849beb58c28d653cc435fe0 (diff)
Diffstat (limited to 'demos/quickstart/protected/pages/Fundamentals')
-rw-r--r--demos/quickstart/protected/pages/Fundamentals/Applications.page2
1 files changed, 1 insertions, 1 deletions
diff --git a/demos/quickstart/protected/pages/Fundamentals/Applications.page b/demos/quickstart/protected/pages/Fundamentals/Applications.page
index 8ea9a1f7..df1418fb 100644
--- a/demos/quickstart/protected/pages/Fundamentals/Applications.page
+++ b/demos/quickstart/protected/pages/Fundamentals/Applications.page
@@ -5,7 +5,7 @@
An application is an instance of <tt>TApplication</tt> or its derived class. It manages modules that provide different functionalities and are loaded when needed. It provides services to end-users. It is the central place to store various parameters used in an application. In a PRADO application, the application instance is the only object that is globally accessible via <tt>Prado::getApplication()</tt> function call.
</p>
<p>
-Applications are configured via <a href="?page=Configurations.AppConfig">application configurations</a>. They are usually created entry scripts like the following,
+Applications are configured via <a href="?page=Configurations.AppConfig">application configurations</a>. They are usually created in entry scripts like the following,
<pre class="source">
require_once('/path/to/prado.php');
$application = new TApplication;