Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 230 of /mod/assign/classes/output/renderer.php: call to core\output\core_renderer->footer()
  • line 3656 of /mod/assign/locallib.php: call to mod_assign\output\renderer->render_footer()
  • line 5935 of /mod/assign/locallib.php: call to assign->view_footer()
  • line 714 of /mod/assign/locallib.php: call to assign->view_submission_page()
  • line 55 of /mod/assign/view.php: call to assign->view()
Callback standard_after_main_region_html in quizaccess_proctoring component should be migrated to new hook callback for core\hook\output\after_standard_main_region_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/after_standard_main_region_html_generation.php: call to get_plugins_with_function()
  • line 614 of /lib/classes/output/core_renderer.php: call to core\hook\output\after_standard_main_region_html_generation->process_legacy_callbacks()
  • line 219 of /lib/mustache/src/Mustache/Context.php: call to core\output\core_renderer->standard_after_main_region_html()
  • line 138 of /lib/mustache/src/Mustache/Context.php: call to Mustache_Context->findVariableInStack()
  • line 120 of /var/www/moodledata/localcache/mustache/1789150141/boost/__Mustache_c40e2718a0b707cf3fea65f99eab3fb2.php: call to Mustache_Context->findDot()
  • line 66 of /lib/mustache/src/Mustache/Template.php: call to __Mustache_c40e2718a0b707cf3fea65f99eab3fb2->renderInternal()
  • line 192 of /lib/classes/output/renderer_base.php: call to Mustache_Template->render()
  • line 107 of /theme/boost/layout/drawers.php: call to core\output\renderer_base->render_from_template()
  • line 972 of /lib/classes/output/core_renderer.php: call to include()
  • line 888 of /lib/classes/output/core_renderer.php: call to core\output\core_renderer->render_page_layout()
  • line 273 of /mod/assign/classes/output/renderer.php: call to core\output\core_renderer->header()
  • line 78 of /lib/classes/output/plugin_renderer_base.php: call to mod_assign\output\renderer->render_assign_header()
  • line 5908 of /mod/assign/locallib.php: call to core\output\plugin_renderer_base->render()
  • line 714 of /mod/assign/locallib.php: call to assign->view_submission_page()
  • line 55 of /mod/assign/view.php: call to assign->view()
ENGL210: Writing Activity: Effective Emails | Saylor University
Skip to main content
Saylor University
  • Home
  • Calendar
  • mySaylor
  • More
Sitewide search Close
Toggle search input
You are currently using guest access
Log in
Saylor University
Home Calendar mySaylor
Expand all Collapse all
  1. ENGL210: Technical Writing
  2. Unit 2: Internal Communication: Writing Memos and Emails
  3. 2.2: Major Topic Emails
  4. 2.2.2: Best Practices for Emails
  5. Writing Activity: Effective Emails

Writing Activity: Effective Emails

Completion requirements
Make a submission
In a paragraph (50–100 words), review the subject lines of emails you have received. What made them effective or ineffective? What role does a subject line play? In a second paragraph, critically examine the formatting of several of the emails you have received or sent. Do they meet the standard of using line breaks or whitespace and being concise (under three paragraphs)? Why is formatting key in emails? How does save time for both the sender and the reader?
Back to '2.2.2: Best Practices for Emails'
You are currently using guest access (Log in)
Data retention summary
Get the mobile app
Powered by Moodle