{"id":36179,"date":"2025-05-21T15:00:34","date_gmt":"2025-05-21T09:30:34","guid":{"rendered":"https:\/\/www.editage.com\/insights\/?p=36179"},"modified":"2025-05-21T14:58:05","modified_gmt":"2025-05-21T09:28:05","slug":"clearer-research-wider-reach-avoid-these-common-mistakes-in-plain-language-summaries","status":"publish","type":"post","link":"https:\/\/www.editage.com\/insights\/clearer-research-wider-reach-avoid-these-common-mistakes-in-plain-language-summaries","title":{"rendered":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries"},"content":{"rendered":"

In medical research, good science is only part of the story. To make a real-world impact, discovery alone isn\u2019t enough. The findings need to reach people beyond the lab. This means not just the wider academic community, but also patients, caregivers, policymakers, and the public. And it all starts with clear communication. One way to do this is through a Plain Language Summary (PLS) or lay summary, which has become valuable in research communication<\/a>. As the name suggests, a PLS is a simplified version of a study designed to make your work accessible to readers without specialist knowledge. But writing one well requires a different approach<\/a>, and it can be surprisingly easy to get it wrong.<\/p>\n

If you’ve ever struggled to write a PLS, you’re not alone. It’s not because you’re unclear or careless, it’s more often because you’ve spent years mastering a type of writing (typically suited for scholarly journals) meant for precision, not necessarily wider accessibility and understanding. So, when it comes to explaining your research in everyday terms, it’s like switching to a dialect you’ve never formally learned.<\/p>\n

Writing plainly doesn\u2019t mean diluting your science. It means reshaping it so that more people can see its value. The good news? You\u2019ve already nailed the tough part: knowing the research and data in and out. Now it’s just about building the bridge. Let\u2019s look at the most common mistakes researchers make when writing PLS and how you can steer clear of them.<\/p>\n

1. Using technical jargon without realizing it<\/strong><\/h3>\n

One of the most common mistakes in PLS writing is using jargon<\/a>. Even terms that feel basic within your specialty can be confusing or misinterpreted by non-experts, or they may even stop reading it. For instance, you might not think twice before using words like \u201ccohort,\u201d \u201cintravenous,\u201d or \u201cdouble-blinding,\u201d but to someone outside your field, such terms can be roadblocks to understanding your message.<\/p>\n

What to try instead:<\/strong> Replace technical words with plain alternatives when possible. If a term or abbreviation is essential, define it briefly. Tools like the CDC\u2019s Plain Language Thesaurus<\/a> can also help translate complex scientific language without losing accuracy. Once your draft is ready, go through it with fresh eyes. You can also ask someone outside your field to review it.<\/p>\n

2. Writing in an academic tone and style<\/strong><\/h3>\n

Old habits die hard! After years of writing for academic journals and peers, it\u2019s second nature to fall back on an academic tone. But when it comes to PLS, such a writing style can make your research feel distant, formal, and hard to follow. Instead, it should be easy to read<\/a>, and sound more like you\u2019re explaining your work in conversation, rather than presenting it at a conference. For example<\/a>, use simple words, short, active sentences; direct phrasing; and a clear, logical structure.<\/p>\n

What to try instead: <\/strong>Use active voice, for instance, “Researchers found…” instead of “It was found…”. Lead with the most important takeaway, then the supporting and background information. Keep the sentences short enough that someone can absorb them easily on the first read. Paragraphs should break information into sections with clear headings rather than having dense blocks of text. You can also use bullet points and text bolding (for emphasis), when required, but be intentional and don\u2019t overuse it. When mentioning data or outcomes, guide the reader by putting numbers into everyday terms. Rather than overwhelming readers with statistics, highlight the meaning behind them: what is higher, what is lower, what is better, and why it matters. Where possible, use words over symbols and avoid piling numbers together without explanation.<\/p>\n

3. Oversimplifying to the point of inaccuracy<\/strong><\/h3>\n

In trying to make research easier to understand, it\u2019s possible to oversimplify<\/a> so much that the nuance, significance, or implications of the work are lost. Oversimplifying can not only weaken your message but also distort the science itself. For example, saying \u201cThe treatment worked\u201d might sound clear, but it leaves out who it worked for, how well it worked, and under what conditions. A layperson could walk away with the wrong idea or interpretation of your work.<\/p>\n

What to try instead: <\/strong>Simplify the language, not the meaning. Break down complex ideas into smaller steps. Keep important details or conditions. Use relatable comparisons if needed, but never at the expense of accuracy.<\/p>\n

4. Forgetting the reader\u2019s perspective<\/strong><\/h3>\n

Before you can frame your summary clearly, you need to recognize who your audience is and what matters to them most. You can skip dense background details or literature reviews that aren\u2019t crucial for basic understanding, but you need to give them context. This is because you know why your research matters, but your reader might not<\/a>. One common misstep is assuming readers already understand the context, the background, the problem you’re addressing, or why your findings are important. Without this framing, even a perfectly simplified summary can leave readers wondering: So what? While they may not need a full history of the field, they do want to know the essentials: what the study is about, why it matters, and how it could affect them.<\/p>\n

What to try instead: <\/strong>Think of it as setting the stage<\/a>: why the research matters, what problem is addressed, who it impacts, what\u2019s new, and what might change because of it. Start by putting yourself in your audience\u2019s shoes<\/a> and ask yourself what questions they would have when reading your study. Focus your summary on answering those questions. Moreover, it\u2019s not enough to just present the facts, you also need to help readers understand what they mean in real life, for instance, does it suggest a new treatment possibility, a policy change, or simply deeper understanding? So, spell out why the findings matter, and who could be impacted.<\/p>\n

5. Overlooking sensitivity <\/strong><\/h3>\n

Plain language writing focuses on clarity, but when discussing sensitive health topics, clarity alone isn’t enough. Without care, a summary can come across as cold, dismissive, or even unintentionally stigmatizing. Lay summaries often cover research involving vulnerable populations, serious illnesses, mental health, or life-altering conditions, and the way your message is delivered needs an extra layer of sensitivity and thoughtfulness<\/a>. You must strike a balance between informing without causing unnecessary fear, false hope, or reinforcing stigma.<\/p>\n

What to try instead: <\/strong>Use respectful language, for example<\/a>, “people living with diabetes” rather than “diabetics”. Avoid overpromising outcomes or making the research sound more definitive than it is. Be careful with emotionally loaded terms; stick to factual, clear descriptions that recognize the complexity of patient experiences. Think about how someone personally affected by the condition might feel when reading your summary and write with that empathy and care in mind.<\/p>\n

When done right, PLS can bridge the gap between research and understanding without losing the science that matters. By avoiding these common mistakes, you can help ensure that your research is understood by the people it\u2019s meant to serve.<\/p>\n","protected":false},"excerpt":{"rendered":"

In medical research, good science is only part of the story. To make a real-world impact, discovery alone isn\u2019t enough. The findings need to reach people beyond the lab. This means not just the wider academic community, but also patients, caregivers, policymakers, and the public. And it all starts with clear communication. One way to […]<\/p>\n","protected":false},"author":2739,"featured_media":36180,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[2412],"tags":[],"new_categories":[],"new_tags":[5786,2965],"series":[],"class_list":["post-36179","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plain-language-summaries","new_tags-plain-language-summary","new_tags-science-communication"],"acf":[],"yoast_head":"\nClearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights<\/title>\n<meta name=\"description\" content=\"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.editage.com\/insights\/?p=36179\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights\" \/>\n<meta property=\"og:description\" content=\"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.editage.com\/insights\/?p=36179\" \/>\n<meta property=\"og:site_name\" content=\"Editage Insights\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/Editage\" \/>\n<meta property=\"article:published_time\" content=\"2025-05-21T09:30:34+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"8192\" \/>\n\t<meta property=\"og:image:height\" content=\"5464\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Nisha Nair\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Editage\" \/>\n<meta name=\"twitter:site\" content=\"@Editage\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nisha Nair\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179\"},\"author\":{\"name\":\"Nisha Nair\",\"@id\":\"https:\/\/www.editage.com\/insights\/#\/schema\/person\/61acfd299e35750234c24df22d65c90d\"},\"headline\":\"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries\",\"datePublished\":\"2025-05-21T09:30:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179\"},\"wordCount\":1175,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.editage.com\/insights\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg\",\"articleSection\":[\"Plain Language Summaries\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.editage.com\/insights\/?p=36179#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179\",\"url\":\"https:\/\/www.editage.com\/insights\/?p=36179\",\"name\":\"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights\",\"isPartOf\":{\"@id\":\"https:\/\/www.editage.com\/insights\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg\",\"datePublished\":\"2025-05-21T09:30:34+00:00\",\"description\":\"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.editage.com\/insights\/?p=36179\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage\",\"url\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg\",\"contentUrl\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg\",\"width\":8192,\"height\":5464},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.editage.com\/insights\/?p=36179#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.editage.com\/insights\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.editage.com\/insights\/#website\",\"url\":\"https:\/\/www.editage.com\/insights\/\",\"name\":\"Editage Insights\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.editage.com\/insights\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.editage.com\/insights\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.editage.com\/insights\/#organization\",\"name\":\"Editage Insights\",\"url\":\"https:\/\/www.editage.com\/insights\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.editage.com\/insights\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2024\/09\/editage-insights-logo-1-scaled.webp\",\"contentUrl\":\"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2024\/09\/editage-insights-logo-1-scaled.webp\",\"width\":2560,\"height\":324,\"caption\":\"Editage Insights\"},\"image\":{\"@id\":\"https:\/\/www.editage.com\/insights\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/Editage\",\"https:\/\/x.com\/Editage\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.editage.com\/insights\/#\/schema\/person\/61acfd299e35750234c24df22d65c90d\",\"name\":\"Nisha Nair\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.editage.com\/insights\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/660189fe419f6fb3e9fb75da14e91353d73a8949778b5771bd41f7682fb28a14?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/660189fe419f6fb3e9fb75da14e91353d73a8949778b5771bd41f7682fb28a14?s=96&d=mm&r=g\",\"caption\":\"Nisha Nair\"},\"url\":\"https:\/\/www.editage.com\/insights\/nishanair1\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights","description":"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.editage.com\/insights\/?p=36179","og_locale":"en_US","og_type":"article","og_title":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights","og_description":"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.","og_url":"https:\/\/www.editage.com\/insights\/?p=36179","og_site_name":"Editage Insights","article_publisher":"https:\/\/www.facebook.com\/Editage","article_published_time":"2025-05-21T09:30:34+00:00","og_image":[{"width":8192,"height":5464,"url":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg","type":"image\/jpeg"}],"author":"Nisha Nair","twitter_card":"summary_large_image","twitter_creator":"@Editage","twitter_site":"@Editage","twitter_misc":{"Written by":"Nisha Nair","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.editage.com\/insights\/?p=36179#article","isPartOf":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179"},"author":{"name":"Nisha Nair","@id":"https:\/\/www.editage.com\/insights\/#\/schema\/person\/61acfd299e35750234c24df22d65c90d"},"headline":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries","datePublished":"2025-05-21T09:30:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179"},"wordCount":1175,"commentCount":0,"publisher":{"@id":"https:\/\/www.editage.com\/insights\/#organization"},"image":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage"},"thumbnailUrl":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg","articleSection":["Plain Language Summaries"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.editage.com\/insights\/?p=36179#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.editage.com\/insights\/?p=36179","url":"https:\/\/www.editage.com\/insights\/?p=36179","name":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries | Editage Insights","isPartOf":{"@id":"https:\/\/www.editage.com\/insights\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage"},"image":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage"},"thumbnailUrl":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg","datePublished":"2025-05-21T09:30:34+00:00","description":"Writing a strong Plain Language Summary (PLS) or lay summary requires a different approach compared to traditional academic writing, and it can be surprisingly easy to get it wrong. We explore the most common mistakes researchers make when writing a PLS and how to avoid them.","breadcrumb":{"@id":"https:\/\/www.editage.com\/insights\/?p=36179#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.editage.com\/insights\/?p=36179"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.editage.com\/insights\/?p=36179#primaryimage","url":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg","contentUrl":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2025\/05\/pexels-cup-of-couple-8015679.jpg","width":8192,"height":5464},{"@type":"BreadcrumbList","@id":"https:\/\/www.editage.com\/insights\/?p=36179#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.editage.com\/insights\/"},{"@type":"ListItem","position":2,"name":"Clearer Research, Wider Reach: Avoid These Common Mistakes in Plain Language Summaries"}]},{"@type":"WebSite","@id":"https:\/\/www.editage.com\/insights\/#website","url":"https:\/\/www.editage.com\/insights\/","name":"Editage Insights","description":"","publisher":{"@id":"https:\/\/www.editage.com\/insights\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.editage.com\/insights\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.editage.com\/insights\/#organization","name":"Editage Insights","url":"https:\/\/www.editage.com\/insights\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.editage.com\/insights\/#\/schema\/logo\/image\/","url":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2024\/09\/editage-insights-logo-1-scaled.webp","contentUrl":"https:\/\/www.editage.com\/insights\/wp-content\/uploads\/2024\/09\/editage-insights-logo-1-scaled.webp","width":2560,"height":324,"caption":"Editage Insights"},"image":{"@id":"https:\/\/www.editage.com\/insights\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/Editage","https:\/\/x.com\/Editage"]},{"@type":"Person","@id":"https:\/\/www.editage.com\/insights\/#\/schema\/person\/61acfd299e35750234c24df22d65c90d","name":"Nisha Nair","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.editage.com\/insights\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/660189fe419f6fb3e9fb75da14e91353d73a8949778b5771bd41f7682fb28a14?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/660189fe419f6fb3e9fb75da14e91353d73a8949778b5771bd41f7682fb28a14?s=96&d=mm&r=g","caption":"Nisha Nair"},"url":"https:\/\/www.editage.com\/insights\/nishanair1"}]}},"_links":{"self":[{"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/posts\/36179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/users\/2739"}],"replies":[{"embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/comments?post=36179"}],"version-history":[{"count":0,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/posts\/36179\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/media\/36180"}],"wp:attachment":[{"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/media?parent=36179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/categories?post=36179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/tags?post=36179"},{"taxonomy":"new_categories","embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/new_categories?post=36179"},{"taxonomy":"new_tags","embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/new_tags?post=36179"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.editage.com\/insights\/wp-json\/wp\/v2\/series?post=36179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}