Index: openacs-4/packages/acs-messaging/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.adp,v diff -u -r1.2.2.4 -r1.2.2.5 --- openacs-4/packages/acs-messaging/www/doc/requirements.adp 9 Jun 2016 13:03:12 -0000 1.2.2.4 +++ openacs-4/packages/acs-messaging/www/doc/requirements.adp 5 Jul 2016 12:15:32 -0000 1.2.2.5 @@ -46,9 +46,9 @@

IV. Use-cases and User Scenarios

ACS Messaging is generally not used directly by users, so there are no user interface level scenarios to consider at this point. -It's possible that in the future we will want to extend the system -with generic administrative user interfaces, but this is not clear -right now.

+It's possible that in the future we will want to extend the +system with generic administrative user interfaces, but this is not +clear right now.

We scenarios that we should consider are the kinds of applications that we mean to support with this package, and what the developers of those applications would like to see in the data @@ -59,8 +59,8 @@

  • BBoard
  • Webmail
  • General Comments
  • Spam
  • Various parts of the ticket tracker.
  • Each of these applications requires a message store and each -defines it's own high level organization for messages whithin that -store.

    +defines it's own high level organization for messages whithin +that store.