Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp,v
diff -u -r1.1.2.2 -r1.1.2.3
--- openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp 13 Jul 2023 12:44:56 -0000 1.1.2.2
+++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.adp 30 Jul 2024 18:05:34 -0000 1.1.2.3
@@ -47,7 +47,7 @@
user/password)
Password Management (where to update passwords)Account Registration (where to create new accounts)On-Demand Sync (to get user info from the source in real
time)
-Those configurations simply will perform the tcl proc that is
+
Those configurations simply will perform the Tcl proc that is
defined in the SC above described for the given SC implementation
that you choose. In other words:
@@ -79,7 +79,7 @@
under Security section. If username is used for logging, it will
ask for the authority to use, since username is unique by authority
but not for the entire openacs installation (can exists several
-identic usernames but each one belongs to a different
+identical usernames but each one belongs to a different
authority).
acs-authentication defines a set of SC to
@@ -116,7 +116,7 @@
- The user enters the email/user & password
- It will search the user in the users table and return the
authority_id
- With that authority_id it will find the respective SC
-implementation which contains the adequate tcl proc for the
+implementation which contains the adequate Tcl proc for the
authentication process
- That proc will check the identity of the user based on the
password (right now could be locally, pam or ldap authenticated,
Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp,v
diff -u -r1.4.2.4 -r1.4.2.5
--- openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp 13 Jul 2023 12:44:56 -0000 1.4.2.4
+++ openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.adp 30 Jul 2024 18:05:34 -0000 1.4.2.5
@@ -125,7 +125,7 @@
. Create and name an
authority (in the sitewide admin UI)
Set Authentication to PAM.
If the PAM domain defines a password command, you can set Password
Management to PAM. If not, the PAM module cannot change the
-user's password and you should leave this option Disabled.
Leave Account Registration disabed.
Configure Batch
+user's password and you should leave this option Disabled.
Leave Account Registration disabled.
Configure Batch
Synchronization
Index: openacs-4/packages/acs-mail-lite/www/doc/analysis-notes.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/analysis-notes.adp,v
diff -u -r1.3.2.2 -r1.3.2.3
--- openacs-4/packages/acs-mail-lite/www/doc/analysis-notes.adp 27 Apr 2022 16:21:06 -0000 1.3.2.2
+++ openacs-4/packages/acs-mail-lite/www/doc/analysis-notes.adp 30 Jul 2024 18:08:39 -0000 1.3.2.3
@@ -75,7 +75,7 @@
And yet, predicting the duration of the future process is difficult.
- What if the email is 10MB and needs parsed, whereas all prior emails were less then 10kb?
+ What if the email is 10MB and needs parsed, whereas all prior emails were less than 10kb?
What if one of the callbacks converts a pdf into a png and annotates it for a web view and takes a few minutes?
What if the next 5 emails have callbacks that take 5 to 15 minutes to process each waiting on an external service?
@@ -119,7 +119,7 @@
Prioritized stack processing cycle
- If next cylce starts and current cycle is still running,
+ If next cycle starts and current cycle is still running,
set scan_in_est_dur_per_cycle_s_override to actual wait time the current cycle has to wait including any prior cycle wait time --if the delays exceed one cycle (accumulative_delay_cycles.
From acs-tcl/tcl/test/ad-proc-test-procs.tcl
Index: openacs-4/packages/acs-mail-lite/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/index.adp,v
diff -u -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/acs-mail-lite/www/doc/index.adp 27 Apr 2022 16:21:06 -0000 1.4.2.2
+++ openacs-4/packages/acs-mail-lite/www/doc/index.adp 30 Jul 2024 18:08:39 -0000 1.4.2.3
@@ -42,7 +42,7 @@
bounced mail then his bounce-record gets deleted since it can be
assumed that his email account is working again and no longer
refusing emails. This value can be changed with the parameter
-"MaxDaysToBounce".
If more then Y emails were returned by a particular user then
+"MaxDaysToBounce".If more than Y emails were returned by a particular user then
his email account gets disabled from receiving any more mails from
the system by setting the email_bouncing_p flag to t. This value
can be changed with the parameter "MaxBounceCount".To notify users that they will not receive any more mails and
Index: openacs-4/packages/acs-mail-lite/www/doc/outbound.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/outbound.adp,v
diff -u -r1.2.2.2 -r1.2.2.3
--- openacs-4/packages/acs-mail-lite/www/doc/outbound.adp 27 Apr 2022 16:21:06 -0000 1.2.2.2
+++ openacs-4/packages/acs-mail-lite/www/doc/outbound.adp 30 Jul 2024 18:08:39 -0000 1.2.2.3
@@ -76,7 +76,7 @@
be assumed that his email account is working again and no longer
refusing emails. This value can be changed with the parameter
"MaxDaysToBounce".
-If more then Y emails were returned by a particular user then
+If more than Y emails were returned by a particular user then
his email account gets disabled from receiving any more mails
from the system by setting the email_bouncing_p flag to t. This
value can be changed with the parameter "MaxBounceCount".