author | Michael Krelin <hacker@klever.net> | 2005-04-02 17:08:40 (UTC) |
---|---|---|
committer | Michael Krelin <hacker@klever.net> | 2005-04-02 17:08:40 (UTC) |
commit | 1a234a03b327b20bf7490c696ebc41a9d65117ac (patch) (side-by-side diff) | |
tree | 8a62fb61dcb8abc7b9dab3bae68d7f4088224435 | |
parent | 8e7ab6661815e333ee9377c2655a03aee89372c2 (diff) | |
download | sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.zip sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.tar.gz sitecing-1a234a03b327b20bf7490c696ebc41a9d65117ac.tar.bz2 |
typo corrected
-rw-r--r-- | htdocs/exceptions/index.chtml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/htdocs/exceptions/index.chtml b/htdocs/exceptions/index.chtml index e66620a..6bb2a3c 100644 --- a/htdocs/exceptions/index.chtml +++ b/htdocs/exceptions/index.chtml @@ -10,13 +10,13 @@ <%method void content() %> <h1>site-C-ing exception handling</h1> <p> The purpose of this section is to give an overview of the <em>site-C-ing</em> exception handling mechanism. Before the web visitor can see the page each site-C-ing component goes through a few stages, namely, preprocessing, - compiling and execution. Having three stages to go through also means the + compiling and execution. Having three stages to go through also means three stages one can fail to go through and three exciting opportunities to handle different errors. </p> <p> First each component is preprocessed so that you can feed the valid c++ code to the compiler. Here is where the preprocessor can choke at your broken |