Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v
diff -u -r1.60.2.11 -r1.60.2.12
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 27 Apr 2022 12:22:29 -0000 1.60.2.11
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 5 Feb 2024 15:35:07 -0000 1.60.2.12
@@ -178,7 +178,7 @@
The OpenACS templating system allows you to give your site a consistent look and feel. It also promotes code maintainability in the presentation layer, by allowing presentation components to be reused across multiple pages. If you need to change the layout for some reason, then you only need to make that change in one location, instead of across many files.
- In this problem set you will familiarise yourself with the templating system in openacs. This will be achieved through customising an existing edit-this-page application template.
+ In this problem set you will familiarize yourself with the templating system in OpenACS. This will be achieved through customizing an existing edit-this-page application template.
Before proceeding, it is strongly advised to read the templating documentation on your OpenACS installation (http://localhost:8000/doc/acs-templating). The documentation lists the special tags available for ADP files.
@@ -571,7 +571,7 @@
note-edit.tcl requires a
note_id to determine which record
should be deleted. It also looks for a confirmation variable, which
-should initially be absert. If it is absent, we create a form to
+should initially be absent. If it is absent, we create a form to
allow the user to confirm the deletion. Note that in
entry-edit.tcl we used ad_form to access the Form Template
commands; here, we call them directly because we don't need the extra