Index: openacs-4/packages/acs-subsite/tcl/subsite-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/tcl/subsite-procs.tcl,v diff -u -N -r1.68.2.6 -r1.68.2.7 --- openacs-4/packages/acs-subsite/tcl/subsite-procs.tcl 16 May 2019 09:54:29 -0000 1.68.2.6 +++ openacs-4/packages/acs-subsite/tcl/subsite-procs.tcl 5 Oct 2019 13:01:38 -0000 1.68.2.7 @@ -1180,8 +1180,7 @@ ad_proc -private subsite::assert_user_may_add_member {} { Used on pages that add users to the application group of - the current subsite to assert that the currently logged in - user may add users. + the current subsite to assert that the currently logged-in user may add users. @author Peter Marklund } { Index: openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.adp,v diff -u -N -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.adp 25 Apr 2018 08:40:23 -0000 1.4 +++ openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.adp 5 Oct 2019 13:01:38 -0000 1.4.2.1 @@ -171,8 +171,8 @@
  1. Go back to the admin page (/admin)
  2. Click on the Groups -> GuideStar.org. Add ArsDigita as a component
  3. Remove the composition rel type from this -group
  4. Readd the composition rel type. Make sure arsdigita -doesn't show up
  5. remove the composition rel type
  6. Add a permissible rel type: +group
  7. Re-add the composition rel type. Make sure arsdigita +doesn't show up
  8. Remove the composition rel type
  9. Add a permissible rel type: project_lead_relation
  10. Click yes to create a rel segment named "GuideStar Project Leads"
  11. Go back to /admin/groups
  12. Click on "relationship to site"
  13. Remove yourself from the group.
  14. Add yourself again as a member (using the membership relation). You will have to select an existing party from the Index: openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html,v diff -u -N -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html 7 Aug 2017 23:47:59 -0000 1.4 +++ openacs-4/packages/acs-subsite/www/doc/group-admin-pages-acceptance-test.html 5 Oct 2019 13:01:38 -0000 1.4.2.1 @@ -268,9 +268,9 @@
  15. Remove the composition rel type from this group -
  16. Readd the composition rel type. Make sure arsdigita doesn't show up +
  17. Re-add the composition rel type. Make sure arsdigita doesn't show up -
  18. remove the composition rel type +
  19. Remove the composition rel type
  20. Add a permissible rel type: project_lead_relation Index: openacs-4/packages/acs-subsite/www/shared/community-member.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/shared/community-member.tcl,v diff -u -N -r1.25.2.1 -r1.25.2.2 --- openacs-4/packages/acs-subsite/www/shared/community-member.tcl 16 May 2019 09:54:29 -0000 1.25.2.1 +++ openacs-4/packages/acs-subsite/www/shared/community-member.tcl 5 Oct 2019 13:01:38 -0000 1.25.2.2 @@ -1,7 +1,7 @@ ad_page_contract { shows User A what User B has contributed to the community - @param user_id defaults to currently logged in user if there is one + @param user_id defaults to currently logged-in user if there is one @cvs-id $Id$ } { {user_id:naturalnum ""} Index: openacs-4/packages/acs-subsite/www/user/basic-info-update.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-subsite/www/user/basic-info-update.tcl,v diff -u -N -r1.17 -r1.17.2.1 --- openacs-4/packages/acs-subsite/www/user/basic-info-update.tcl 7 Aug 2017 23:47:59 -0000 1.17 +++ openacs-4/packages/acs-subsite/www/user/basic-info-update.tcl 5 Oct 2019 13:01:38 -0000 1.17.2.1 @@ -1,5 +1,5 @@ ad_page_contract { - Displays form for currently logged in user to update his/her personal information + Displays form for currently logged-in user to update his/her personal information @author Unknown @creation-date Unknown Index: openacs-4/packages/categories/www/doc/design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/categories/www/doc/design.adp,v diff -u -N -r1.3 -r1.3.2.1 --- openacs-4/packages/categories/www/doc/design.adp 30 Apr 2018 09:04:46 -0000 1.3 +++ openacs-4/packages/categories/www/doc/design.adp 5 Oct 2019 13:07:21 -0000 1.3.2.1 @@ -35,8 +35,8 @@ The mapped subtree will consist of all subcategories of the category the user selected - the category itself will not be included. Note that the mapped subtree will not be a new tree. -Therefore this option should be used only if an admin plans to use -the subtree 'as is' and has no intention of making changes +Therefore, this option should be used only if an admin plans to use +the subtree as-is and has no intention of making changes to it.

    An alternative solution is available for admins who want to create a tree by copying one of the existing trees and subsequently Index: openacs-4/packages/categories/www/doc/design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/categories/www/doc/design.html,v diff -u -N -r1.3 -r1.3.2.1 --- openacs-4/packages/categories/www/doc/design.html 7 Aug 2017 23:48:05 -0000 1.3 +++ openacs-4/packages/categories/www/doc/design.html 5 Oct 2019 13:07:21 -0000 1.3.2.1 @@ -36,9 +36,9 @@ a "Map subtree" link, after which they will see a list of tree nodes.
    The mapped subtree will consist of all subcategories of the category the user selected - the category itself will not be included. -Note that the mapped subtree will not be a new tree. Therefore -this option should be used only if an admin plans to use the subtree 'as -is' and has no intention of making changes to it. +Note that the mapped subtree will not be a new tree. Therefore, +this option should be used only if an admin plans to use the subtree +as-is and has no intention of making changes to it.

    An alternative solution is available for admins who want to create a tree by copying one of the existing trees and subsequently