{"id":2278,"date":"2017-04-21T10:33:26","date_gmt":"2017-04-21T09:33:26","guid":{"rendered":"https:\/\/blogs.ncl.ac.uk\/web\/?p=2278"},"modified":"2017-04-20T15:34:24","modified_gmt":"2017-04-20T14:34:24","slug":"check-your-spelling-and-grammar-as-you-type","status":"publish","type":"post","link":"https:\/\/blogs.ncl.ac.uk\/web\/2017\/04\/21\/check-your-spelling-and-grammar-as-you-type\/","title":{"rendered":"Check Your Spelling and Grammar as You Type"},"content":{"rendered":"<p>Content evaluation tools, like Siteimprove, help you to fix problems like misspellings on your live website. But what about catching the mistakes before they&#8217;re made public?<\/p>\n<p>For the past month or so I&#8217;ve been testing a browser-based spelling and grammar checker that highlights any issues as you type. It&#8217;s called <a href=\"https:\/\/www.grammarly.com\/\">Grammarly<\/a>. You might have seen one of their ads as you&#8217;ve waited for a video to play on YouTube?<\/p>\n<p>Add the <a href=\"https:\/\/chrome.google.com\/webstore\/detail\/grammarly-for-chrome\/kbfnbcaeplbcioakkpcpgfkobkghlhen?hl=en\">browser extension to Chrome<\/a> and you&#8217;re ready to go.<\/p>\n<p>The extension works in most browser-based text editors, from webmail to social media and of course, T4. As you type you&#8217;ll see errors highlighted in red. When you hover over them an explanation of why they&#8217;ve been picked up is given along with suggested corrections. Just like the spellchecker in Word, you can review the identified errors and choose to accept or ignore them.<\/p>\n<p><a href=\"https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-large wp-image-2284\" src=\"https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4-1024x348.jpg\" alt=\"Screenshot of Grammarly spelling correction in T4\" width=\"584\" height=\"198\" srcset=\"https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4-1024x348.jpg 1024w, https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4-300x102.jpg 300w, https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4-768x261.jpg 768w, https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4-500x170.jpg 500w, https:\/\/blogs.ncl.ac.uk\/web\/files\/2017\/04\/grammarly-t4.jpg 1439w\" sizes=\"auto, (max-width: 584px) 100vw, 584px\" \/><\/a><\/p>\n<p>You can choose to sign up for a free account (although it&#8217;s not necessary) to get access to additional features:<\/p>\n<ul>\n<li>choose British English rules for spelling, punctuation, and grammar<\/li>\n<li>add words to your personal dictionary<\/li>\n<li>write directly in Grammarly or upload documents for checking<\/li>\n<\/ul>\n<p>It&#8217;s not perfect, and I&#8217;d advise you to read the explanations and use your judgment as to whether you accept them or not. It&#8217;s also not a substitute for proofreading your content before it&#8217;s published, but it&#8217;s a pretty good tool to help you take a step towards minimising spelling mistakes and grammatical errors.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Content evaluation tools, like Siteimprove, help you to fix problems like misspellings on your live website. But what about catching the mistakes before they&#8217;re made public? For the past month or so I&#8217;ve been testing a browser-based spelling and grammar &hellip; <a href=\"https:\/\/blogs.ncl.ac.uk\/web\/2017\/04\/21\/check-your-spelling-and-grammar-as-you-type\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":755,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,19],"tags":[26],"class_list":["post-2278","post","type-post","status-publish","format-standard","hentry","category-content","category-tools","tag-writing-for-the-web"],"_links":{"self":[{"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/posts\/2278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/users\/755"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/comments?post=2278"}],"version-history":[{"count":5,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/posts\/2278\/revisions"}],"predecessor-version":[{"id":2285,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/posts\/2278\/revisions\/2285"}],"wp:attachment":[{"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/media?parent=2278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/categories?post=2278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.ncl.ac.uk\/web\/wp-json\/wp\/v2\/tags?post=2278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}