{"id":15550,"date":"2022-12-27T12:26:32","date_gmt":"2022-12-27T09:26:32","guid":{"rendered":"https:\/\/railsware.com\/blog\/?p=15550"},"modified":"2025-08-15T15:04:41","modified_gmt":"2025-08-15T12:04:41","slug":"how-to-review-and-edit-articles-tips-for-those-who-collaborate-with-content-writers","status":"publish","type":"post","link":"https:\/\/railsware.com\/blog\/how-to-review-and-edit-articles-tips-for-those-who-collaborate-with-content-writers\/","title":{"rendered":"How to Review and Edit Articles"},"content":{"rendered":"\n<div class=\"intro-text\">If you read my previous <a href=\"https:\/\/railsware.com\/blog\/how-to-write-blog-posts\/\">post on how to write articles<\/a>, you\u2019ll already know that creating content can significantly boost your personal development and career. However, not everyone is ready to jump into this exciting activity straightaway. For such developers, designers, QA engineers, product managers, HR, and other specialists, I always offer the format of collaboration with a professional content writer, where you act as a knowledge holder and reviewer. In this post, we share some tips and approaches on how to make such collaboration fruitful and pleasant. Ready, steady, go!<\/div>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-1024x538.jpg\" alt=\"\" class=\"wp-image-15547\" srcset=\"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-1024x538.jpg 1024w, https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-360x189.jpg 360w, https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-768x404.jpg 768w, https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-1536x807.jpg 1536w, https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-2048x1076.jpg 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Why it matters<\/h2>\n\n\n\n<p>Before we get to the reviewing process, let\u2019s clear up why you need to review the materials written by someone else.<\/p>\n\n\n\n<p>First of all,<strong> it\u2019s important to the commercial success of your team<\/strong>. No matter what you\u2019re working on right now, whether it\u2019s your team\u2019s product or you\u2019re on an outstuff\/outsource project \u2013 the work of a content writer is always aimed at bringing value to your team. If it\u2019s an employer branding project, you\u2019ll get a colleague that will take a part of your workload. If it\u2019s a post aimed at attracting clients, you\u2019ll get a chance to work on a new interesting project. If these are tutorials on how to use your team\u2019s product, it will gain new users and the product profitability will increase.&nbsp;<\/p>\n\n\n\n<p>It\u2019s worth mentioning that the era of SEO-optimized content (in its traditional meaning) has gone long ago. Of course, keywords are crucial but keyword stuffing (100 keywords in one single paragraph) can only annoy readers. Today, it\u2019s more important to create really useful content, even for a small group of people than to write viral posts about \u201cBlockchain,\u201d \u201cArtificial Intelligence,\u201d or \u201cAugmented Reality.\u201d The core of a post should be the readers\u2019 problem and its solution. The shorter the better. To create such content, we need in-depth knowledge and hands-on experience in a specific field, like sometimes using tools like a <a href=\"https:\/\/dataforseo.com\/apis\/serp-api\" target=\"_blank\" rel=\"noopener\" title=\"\">SERP API<\/a> to understand the competitive landscape and fine-tune the content strategies. Your knowledge and experience are crucial. Therefore, collaboration is inevitable.<\/p>\n\n\n\n<p>Second of all, <strong>it&#8217;s your reputation that\u2019s at stake<\/strong>. When you cooperate with a content writer on something, your name will be cited as a co-author, or even as a sole author of a piece. The modern employer often checks such <a href=\"https:\/\/enhancv.com\/resume-templates\/\" target=\"_blank\" rel=\"noopener\" title=\"\">things in your resume<\/a>, especially if you apply for the position of senior or lead. So, you had better mind the quality of copies you add to your CV.<\/p>\n\n\n\n<p>If I have convinced you, let\u2019s move on to the most important steps one should take when reviewing and editing materials.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Planning&nbsp;<\/h2>\n\n\n\n<p>That\u2019s right! The collaboration begins way before a content writer starts working on the material. At least it should. Otherwise, it\u2019ll be much harder to check the text you didn\u2019t even know exists. The more you participate before and during the content creation, the easier it will be for you to review it. Here\u2019s why.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>You know the purpose of this content piece and the audience it should attract<\/strong>. Thus, you know exactly what information is going to be new for the readers and what terms, processes, and technologies should be explained.<\/li>\n\n\n\n<li><strong>You contribute to the article plan outlining<\/strong>. You can immediately point out the main aspects that should be fully disclosed in the article. In this case, checking the material will take much less time.<\/li>\n\n\n\n<li><strong>You will have time to prepare examples, screenshots, or other artifacts<\/strong> necessary for the completeness of the material. While the writer is working on the text, you will be able to reflect and remember interesting cases from your experience, which can then be added to the article.<\/li>\n<\/ul>\n\n\n\n<p>Start your cooperation with a meeting to discuss who this article is for, where it will be published, and what problem it will solve for the readers. Make sure that the problem is acute and relevant, and immediately outline the plan of the article. Don&#8217;t be surprised if in the course of the discussion it turns out that you can write a whole series of articles. It&#8217;s even good.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Reviewing and editing<\/h2>\n\n\n\n<p>When the writer hands you the draft, you should remember that even if it\u2019s not the most priority task for you, the writer is waiting for feedback and cannot move the task further. So, don&#8217;t shelve it. It&#8217;s better to immediately schedule the time (an hour or two) to review the task while no one bothers you, and having <a href=\"https:\/\/www.sodapdf.com\/blog\/ultimate-text-editing\/\" target=\"_blank\" rel=\"noopener\" title=\"\">efficient text editing skills<\/a> can significantly streamline this review process. Here\u2019s a step-by-step guide on how to check the materials.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Read the text completely<\/strong>. This is the most frequent problem of reviewers that I encounter when one of the technical specialists is checking my article. They comment on the first paragraph listing everything they believe is missing, and then, somewhere in the middle or at the end of the text, they say: &#8220;Ah, here it is! Ignore my comment from above.&#8221; Text is not a code. Often the main idea can be in the last paragraph. Just accept the idea that you will have to read the article 2-3 times.<\/li>\n\n\n\n<li><strong>Get back to the plan<\/strong>. It is time to remember what content you thought to put in the article from the very beginning, as well as its purpose, and target audience. Mark paragraphs with too much information (bulky explanation, obvious things, repetitions). Also, highlight the pieces where information is lacking. Specify exactly what is missing. This can be an example, context, explanation of a term\/ process\/ technology, etc.<\/li>\n\n\n\n<li><strong>Look for logical errors<\/strong>, such as an omitted step in the instructions, incorrectly described process, wrong term, twisted cause-and-effect relationship, and so on. Remember, writers aren&#8217;t engineers or designers, and they don&#8217;t have the hands-on experience you do. So, briefly explain where exactly the problem is and how to fix it.<\/li>\n\n\n\n<li><strong>Add examples from <\/strong><strong>your<\/strong><strong> experience<\/strong>. Please don\u2019t use examples you have seen somewhere. It\u2019s much better to say something that happened to you. These mini-stories are the insights that make the material unique and catchy.<\/li>\n\n\n\n<li><strong>Write detailed feedback for the copywriter<\/strong>. Consider using a <a href=\"https:\/\/justdone.com\/plagiarism-checker\" target=\"_blank\" rel=\"noopener\" title=\"\">plagiarism detector<\/a> to ensure originality and inform the writer that you have completed the review and explain how the material made you feel (more on that later).<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">How to write comments in the content writer&#8217;s text<\/h2>\n\n\n\n<p>If you are an engineer and have read at least one article on how to conduct a code review, then you already know the basic principles of commenting. However, if this practice is new to you, the following tips will greatly help both you and the writer you work with.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Be as specific as possible<\/strong>. Explain what needs to be reworked and how. It\u2019s crucial to ensure that your colleagues can immediately correct a piece instead of guessing whether they understood you correctly or not. Here are examples of bad comments: &#8220;Everything is wrong here&#8221;, &#8220;I would have said it differently&#8221;, &#8220;I don&#8217;t like it&#8221;, and &#8220;Something is wrong&#8221;.<\/li>\n\n\n\n<li><strong>Be brief<\/strong>. Sometimes reviewers want to explain why the writer&#8217;s idea is incorrect, so they begin to explain technical details and almost the entire history of their professional development. This is all very interesting, of course, but your primary task is to give the writer the necessary information to correct the text. Nothing more.<\/li>\n\n\n\n<li><strong>Forget about sarcasm<\/strong>. Even if certain things seem obvious to you, this is not always true for other people. Sarcasm is not an effective communication tool. It will only lead to misunderstandings or even conflicts. Perhaps right now, you want to add a caustic joke to the comment, but don&#8217;t be surprised if a colleague comes back to you with additional questions and clarifications again and again.<\/li>\n\n\n\n<li><strong>Don&#8217;t repeat yourself<\/strong>. If you see that the same error repeats several times in the text, it\u2019s better not to leave comments on each of them. Leave one comment and note that this point must be corrected throughout the text.<\/li>\n\n\n\n<li><strong>Don\u2019t rewrite the text from scratch<\/strong>. Sometimes reviewers try so hard that they rewrite every sentence, adding more and more comments. This way, you lose all the benefits from cooperation. If you don\u2019t like the style and language of the copy and want to present everything under your own &#8220;sauce&#8221;, then think what would be better in terms of available resources: rewrite the text yourself, or discuss with a content writer what accents they should change\/add to the text.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">How to write feedback<\/h2>\n\n\n\n<p>When the review is completed, you need to send the material back to the writer to process your comments. You can text something like &#8220;I checked and left some comments&#8221; and that would work. But you can also send your detailed impression of the article to give the content writer better feedback about their work and help them grow. Here are the main tips on how to do that.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Start with something good<\/strong>. This is a universal approach to writing feedback and applies to all specialists. This is how you put a person in a positive mood and keep their motivation at a high level.<\/li>\n\n\n\n<li><strong>Describe the main points that need to be reworked<\/strong>. It is not necessary to list all the issues you commented on in the document, only the main ones.<\/li>\n\n\n\n<li><strong>Suggest options for solutions<\/strong>. Again, don&#8217;t repeat everything you&#8217;ve already written in the comments, just the main ideas. Perhaps you know how to depict a difficult text in the form of an illustration or even a video. Or, maybe you remembered an apt example that would make the material even more interesting and easy to understand.<\/li>\n\n\n\n<li><strong>Describe your expectations for further cooperation<\/strong>. It is very important to clarify your next steps. If you left many comments, ask the writer to send you the material for the second review after the rework. If you think that the main idea of \u200b\u200bthe article was lost or blurred, it is worth setting a meeting to discuss everything again.&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Wrapping up<\/h2>\n\n\n\n<p>I want to emphasize that creating content (no matter if you do it on your own or in collaboration with someone) is an extremely useful and interesting activity. It allows you to share your own experience and knowledge with the world and develop in different directions. The only thing that matters is choosing topics that are really interesting for you, and then that passion will also come across to the reader in the form of an engaging and interesting piece of content.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>All the most essential steps when reviewing and editing somebody&#8217;s text and cooperating on content creation<\/p>\n","protected":false},"author":85,"featured_media":15548,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[],"coauthors":["Daria Roshchyna"],"class_list":["post-15550","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-development"],"acf":[],"aioseo_notices":[],"categories_data":[{"name":"Engineering","link":"https:\/\/railsware.com\/blog?category=development"}],"post_thumbnails":"https:\/\/railsware.com\/blog\/wp-content\/uploads\/2022\/12\/Featured-image-1024x538.jpg","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/15550","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/users\/85"}],"replies":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/comments?post=15550"}],"version-history":[{"count":9,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/15550\/revisions"}],"predecessor-version":[{"id":18513,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/posts\/15550\/revisions\/18513"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media\/15548"}],"wp:attachment":[{"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/media?parent=15550"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/categories?post=15550"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/tags?post=15550"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/railsware.com\/blog\/wp-json\/wp\/v2\/coauthors?post=15550"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}