Fixed a few typo in tutorial.

3 files changed, 13 insertions, 5 deletions

diff --git a/UPGRADE b/UPGRADE
index 755a475a..a811738d 100644
--- a/UPGRADE
+++ b/UPGRADE
@@ -2,9 +2,15 @@
          Upgrading Instructions for PRADO Framework v3.0RC1

          ==================================================

 

+!!!IMPORTANT!!!

+

+After upgrading, remember to delete everything under

+your PRADO application's cache and runtime directories.

+

+

 The following upgrading instructions are cumulative. That is,

 if you want to upgrade from version A to version C and there is

-version B between A and C, then you need to following instructions

+version B between A and C, you need to following the instructions

 for both A and B.

 

 

@@ -20,10 +26,12 @@ Upgrading from v3.0b
   TXmlDocument is moved to System.Xml

   TLogger, TLogRouter, TDataFieldAccessor, TSimpleDateFormatter are moved to System.Util

 

+

 Upgrading from v3.0a

 --------------------

 All event names must start with 'On'.

 

+

 Upgrading from v2.x and v1.x

 ----------------------------

 PRADO v3.x is not backward compatible with v2.x and v1.x.
\ No newline at end of file
diff --git a/demos/quickstart/protected/pages/Advanced/Logging.page b/demos/quickstart/protected/pages/Advanced/Logging.page
index a9f6ac4e..ec3e7879 100644
--- a/demos/quickstart/protected/pages/Advanced/Logging.page
+++ b/demos/quickstart/protected/pages/Advanced/Logging.page
@@ -20,7 +20,7 @@ The difference between <tt>Prado::log()</tt> and <tt>Prado::trace()</tt> is  tha
 

 <h2>Message Routing</h2>

 <p>

-Messages logged using the above two functions are kept in memory. To make use of the messages, developers need to route them to specific destinations, such as files, emails, or browser windows. The message routing is managed by <tt>System.Log.TLogRouter</tt> module. When plugged into an application, it can route the messages to different destination in parallel. Currently, PRADO provides three types of routes:

+Messages logged using the above two functions are kept in memory. To make use of the messages, developers need to route them to specific destinations, such as files, emails, or browser windows. The message routing is managed by <tt>System.Util.TLogRouter</tt> module. When plugged into an application, it can route the messages to different destination in parallel. Currently, PRADO provides three types of routes:

 </p>

 <ul>

   <li><tt>TFileLogRoute</tt> - filtered messages are stored in a specified log file. By default, this file is named <tt>prado.log</tt> under the runtime directory of the application. File rotation is provided.</li>

@@ -31,7 +31,7 @@ Messages logged using the above two functions are kept in memory. To make use of
 To enable message routing, plug in and configure the <tt>TLogRouter</tt> module in application configuration,

 </p>

 <com:TTextHighlighter Language="xml" CssClass="source">

-&lt;module id="log" class="System.Log.TLogRouter"&gt;

+&lt;module id="log" class="System.Util.TLogRouter"&gt;

   &lt;route class="TBrowserLogRoute"

       Levels="Info"

       Categories="System.Web.UI.TPage, System.Web.UI.WebControls" /&gt;

@@ -49,7 +49,7 @@ In the above, the <tt>Levels</tt> and <tt>Categories</tt> specify the log and ca
 Messages can be filtered according to their log levels and categories. Each log message is associated with a log level and a category. With levels and categories, developers can selectively retrieve messages that they are interested on.

 </p>

 <p>

-Log levels defined in <tt>System.Log.TLogger</tt> include : <tt>DEBUG</tt>, <tt>INFO</tt>, <tt>NOTICE</tt>, <tt>WARNING</tt>, <tt>ERROR</tt>, <tt>ALERT</tt>, <tt>FATAL</tt>. Messages can be filtered according log level criteria. For example, if a filter specifies <tt>WARNING</tt> and <tt>ERROR</tt> levels, then only those messages that are of <tt>WARNING</tt> and <tt>ERROR</tt> will be returned.

+Log levels defined in <tt>System.Util.TLogger</tt> include : <tt>DEBUG</tt>, <tt>INFO</tt>, <tt>NOTICE</tt>, <tt>WARNING</tt>, <tt>ERROR</tt>, <tt>ALERT</tt>, <tt>FATAL</tt>. Messages can be filtered according log level criteria. For example, if a filter specifies <tt>WARNING</tt> and <tt>ERROR</tt> levels, then only those messages that are of <tt>WARNING</tt> and <tt>ERROR</tt> will be returned.

 </p>

 <p>

 Message categories are hierarchical. A category whose name is the prefix of another is said to be the ancestor category of the other category. For example, <tt>System.Web</tt> category is the ancestor of <tt>System.Web.UI</tt> and <tt>System.Web.UI.WebControls</tt> categories. Messages can be selectively retrieved using such hierarchical category filters. For example, if the category filter is <tt>System.Web</tt>, then all messages in the <tt>System.Web</tt> are returned. In addition, messages in the childd categories, such as <tt>System.Web.UI.WebControls</tt>, are also returned.

diff --git a/demos/quickstart/protected/pages/Advanced/Performance.page b/demos/quickstart/protected/pages/Advanced/Performance.page
index 0f65e61b..ed0cc6f8 100644
--- a/demos/quickstart/protected/pages/Advanced/Performance.page
+++ b/demos/quickstart/protected/pages/Advanced/Performance.page
@@ -14,7 +14,7 @@ Enabling caching is very easy. Simply add the cache module in the application co
 </p>

 <com:TTextHighlighter Language="xml" CssClass="source">

 &lt;modules&gt;

-    &lt;module id="cache" class="System.Data.TSqliteCache" /&gt;

+    &lt;module id="cache" class="System.Caching.TSqliteCache" /&gt;

 &lt;/modules&gt;

 </com:TTextHighlighter>