{"id":696,"date":"2026-02-25T10:22:53","date_gmt":"2026-02-25T10:22:53","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/"},"modified":"2026-02-25T10:22:53","modified_gmt":"2026-02-25T10:22:53","slug":"rewriting-user-stories-before-after-corrections","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/","title":{"rendered":"Rewriting Examples: Before and After Corrections"},"content":{"rendered":"

Most teams don\u2019t write bad stories because they lack effort\u2014they write them poorly because they don\u2019t know how to spot the flaws. The real problem isn\u2019t the words; it\u2019s the hidden assumptions behind them. I\u2019ve seen stories that sound fine in writing but collapse under scrutiny during sprint planning. The issue? A lack of clarity, testability, or user focus.<\/p>\n

What makes rewriting user stories effective isn\u2019t just grammar or structure\u2014it\u2019s the shift from vague intent to actionable, value-driven clarity. I\u2019ve worked with teams who spent weeks refining stories only to find they were still building features nobody wanted. It wasn\u2019t bad effort. It was bad direction.<\/p>\n

This chapter shows you actual before-and-after examples from real product backlogs. Each rewrite demonstrates a practical fix grounded in real-world team feedback and acceptance criteria failures. You\u2019ll see how small changes in phrasing, structure, and focus can transform a story from untestable noise into a working agreement.<\/p>\n

Flawed vs. Effective: Common Pitfalls and Fixes<\/h2>\n

1. Vague Role, Unclear Purpose<\/h3>\n

Before:<\/strong> As a user, I want to see the data so I can make decisions.<\/p>\n

This story fails because \u201cuser\u201d isn\u2019t specific, and \u201csee the data\u201d is ambiguous. Who is the user? What data? What decisions? There\u2019s no way to test this.<\/p>\n

After:<\/strong> As a sales manager, I want to view weekly performance data by region so I can identify underperforming teams and adjust coaching support.<\/p>\n

Now the role is clear: a sales manager. The data is defined (weekly performance by region), and the outcome is actionable: adjust coaching. This version is testable, focused, and tied to a real business need.<\/p>\n

2. Missing ‘So That’ Clause<\/h3>\n

Before:<\/strong> As a customer, I want to log in with my email and password.<\/p>\n

It states a feature but says nothing about why. The user can\u2019t validate the success of this story without context. Is this for access? For order tracking? The story lacks purpose.<\/p>\n

After:<\/strong> As a returning customer, I want to log in with my email and password so I can view my order history and track delivery status.<\/p>\n

Now the login serves a clear user goal: tracking deliveries. Acceptance criteria can be tied to access, order visibility, and session persistence\u2014each testable and aligned with user needs.<\/p>\n

3. Overly Broad or Untestable Scope<\/h3>\n

Before:<\/strong> As a user, I want to manage my profile so I can update my information.<\/p>\n

\u201cManage\u201d is vague. What can be updated? Name? Address? Preferences? This story could encompass ten different features. It\u2019s too big to test or estimate.<\/p>\n

After:<\/strong> As a registered user, I want to update my email address so I can receive order confirmations at the correct inbox.<\/p>\n

Now the story is about one specific action with a clear outcome. It\u2019s small enough for a sprint, testable with a single validation step, and aligns with user email verification workflows.<\/p>\n

4. Mixing Technical Tasks with User Value<\/h3>\n

Before:<\/strong> As a developer, I want to set up the database connection so the app can load data.<\/p>\n

This sounds like a developer task. But user stories must focus on user outcomes, not developer chores. The story implies the user cares about database connections\u2014a misunderstanding of ownership.<\/p>\n

After:<\/strong> As a customer, I want to see my order history so I can review past purchases and reorder items quickly.<\/p>\n

The technical work (database connection) happens behind the scenes. The user story focuses on the user\u2019s experience: viewing and reordering history. The technical task is embedded in the implementation, not the story.<\/p>\n

5. No Acceptance Criteria or Testable Conditions<\/h3>\n

Before:<\/strong> As a user, I want to search for products so I can find what I need.<\/p>\n

There are no clear success conditions. What happens when I search? What if no results appear? What if the search is slow? Without acceptance criteria, the story is untestable.<\/p>\n

After:<\/strong> As a user, I want to search for products so I can find what I need, with the following acceptance criteria:<\/p>\n

    \n
  • When I enter a product name, the system returns results within 1 second.<\/li>\n
  • If no matches are found, I see a message: \u201cNo results found for \u2018[search term]\u2019\u201d.<\/li>\n
  • If I select a result, I am taken to the product detail page with pricing and availability.<\/li>\n<\/ul>\n

    Now the story has measurable behavior. The development team knows exactly what to build and when it\u2019s done.<\/p>\n

    Practical Framework for Rewriting User Stories<\/h2>\n

    Here\u2019s a simple 4-step method I use with teams to systematically improve stories:<\/p>\n

      \n
    1. Clarify the role:<\/strong> Who is the user? Be specific. Replace \u201cuser\u201d with \u201csales rep,\u201d \u201cadmin,\u201d or \u201ccustomer.\u00a0\u00bb<\/li>\n
    2. Define the action:<\/strong> What exactly do they want to do? Use active verbs: \u201cview,\u201d \u201cupdate,\u201d \u201cfilter,\u201d \u201cexport.\u201d<\/li>\n
    3. State the outcome:<\/strong> Why do they want it? Use \u201cso that\u201d to connect to user or business value.<\/li>\n
    4. Add testable behavior:<\/strong> List 2\u20134 acceptance criteria using Given\/When\/Then format or simple conditions.<\/li>\n<\/ol>\n

      Apply this to any story. You\u2019ll notice how the language tightens, the purpose becomes clear, and the team agrees on what \u201cdone\u201d means.<\/p>\n

      Before-and-After Table: User Story Example Comparison<\/h2>\n

      Here\u2019s a side-by-side comparison of real-world examples to illustrate the transformation.<\/p>\n\n\n\n\n\n\n\n
      Original Story (Flawed)<\/th>\nImproved Story (Actionable)<\/th>\n<\/tr>\n
      As a user, I want to see the dashboard so I can see my data.<\/td>\nAs a project manager, I want to view the team\u2019s sprint burndown chart so I can assess progress and adjust workloads if needed.<\/td>\n<\/tr>\n
      As a customer, I want to save my preferences.<\/td>\nAs a returning customer, I want to save my preferred shipping address so I can speed up checkout for future orders.<\/td>\n<\/tr>\n
      As a user, I want to export reports.<\/td>\nAs a finance analyst, I want to export monthly sales reports in CSV format so I can analyze trends in Excel.<\/td>\n<\/tr>\n
      As a user, I want to update my account.<\/td>\nAs a user, I want to change my password so I can maintain the security of my account.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Each improved version includes a specific role, a clear action, a defined purpose, and is tied to a measurable outcome. These are no longer just requests\u2014they\u2019re working agreements.<\/p>\n

      Key Takeaways<\/h2>\n

      Rewriting user stories isn\u2019t about writing better English\u2014it\u2019s about writing better thinking. The goal isn\u2019t elegance; it\u2019s clarity.<\/p>\n

      When you see a story that starts with \u201cI want to\u2026\u201d and ends with no outcome, pause. Ask: \u201cWho benefits? Why? How will we know it\u2019s done?\u201d That\u2019s where rewriting begins.<\/p>\n

      Use the before-and-after examples as templates. Test every story against these questions:<\/p>\n

        \n
      • Is the user role specific and realistic?<\/li>\n
      • Is the action clear and single-focused?<\/li>\n
      • Does \u201cso that\u201d describe a real user or business outcome?<\/li>\n
      • Are acceptance criteria testable and actionable?<\/li>\n<\/ul>\n

        These are the pillars of a story that gets built correctly\u2014not because developers guessed, but because the team understood it.<\/p>\n

        Frequently Asked Questions<\/h2>\n

        How do I know if a user story needs rewriting?<\/h3>\n

        If the story can\u2019t be tested, if no one on the team can explain the user\u2019s intent, or if it leads to endless questions during refinement, it\u2019s a red flag. A story with missing acceptance criteria or a vague outcome should always be rewritten.<\/p>\n

        Can I rewrite a story after it\u2019s in the backlog?<\/h3>\n

        Yes\u2014constantly. Backlogs evolve. A story that made sense in Sprint 1 may need clarification in Sprint 6. The backlog isn\u2019t a final document. It\u2019s a living conversation. Rewriting is part of refinement, not a sign of failure.<\/p>\n

        Why do teams skip rewriting user stories?<\/h3>\n

        Time pressure, fear of change, or the belief that \u201cthe story is clear enough.\u201d But unclear stories cost more in rework than rewriting ever does. The time spent improving a story is never wasted\u2014it\u2019s preventative.<\/p>\n

        How do I ensure consistency across multiple writers?<\/h3>\n

        Use a shared template and a Definition of Ready checklist. Train your team on the \u201cSo That\u201d rule: every story must end with a clear reason. Run regular story review workshops. Consistency comes from practice and shared standards.<\/p>\n

        Is rewriting user stories a one-time fix?<\/h3>\n

        No. It\u2019s continuous. The same story may need restructuring when the product evolves. The goal isn\u2019t perfection\u2014it\u2019s clarity. Good stories are not static; they grow with the product.<\/p>\n

        What\u2019s the biggest mistake in rewriting user stories?<\/h3>\n

        Adding too much detail too soon. Some teams over-engineer stories with technical jargon or implementation plans. Stay focused on user intent. Let the developers figure out how. The story should be a conversation starter, not a spec.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Most teams don\u2019t write bad stories because they lack effort\u2014they write them poorly because they don\u2019t know how to spot the flaws. The real problem isn\u2019t the words; it\u2019s the hidden assumptions behind them. I\u2019ve seen stories that sound fine in writing but collapse under scrutiny during sprint planning. The issue? A lack of clarity, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":694,"menu_order":1,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-696","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nRewriting User Stories for Clarity and Impact<\/title>\n<meta name=\"description\" content=\"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Rewriting User Stories for Clarity and Impact\" \/>\n<meta property=\"og:description\" content=\"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/\",\"name\":\"Rewriting User Stories for Clarity and Impact\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:22:53+00:00\",\"description\":\"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes in Writing User Stories\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Fixing Bad Stories: Patterns and Remedies\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Rewriting Examples: Before and After Corrections\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Rewriting User Stories for Clarity and Impact","description":"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.","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:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/","og_locale":"fr_FR","og_type":"article","og_title":"Rewriting User Stories for Clarity and Impact","og_description":"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/","name":"Rewriting User Stories for Clarity and Impact","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:22:53+00:00","description":"See real-world user story example comparison: flawed vs improved. Learn how to rewrite user stories that get built right the first time.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/rewriting-user-stories-before-after-corrections\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"Common Mistakes in Writing User Stories","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/"},{"@type":"ListItem","position":3,"name":"Fixing Bad Stories: Patterns and Remedies","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/common-mistakes-in-writing-user-stories\/fixing-bad-user-stories\/"},{"@type":"ListItem","position":4,"name":"Rewriting Examples: Before and After Corrections"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/696","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/696\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/694"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=696"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}