{"id":10710,"date":"2026-08-17T02:00:21","date_gmt":"2026-08-17T02:00:21","guid":{"rendered":"https:\/\/certitranslate.com\/common-technical-translation-terminology-errors\/"},"modified":"2026-09-04T12:42:09","modified_gmt":"2026-09-04T12:42:09","slug":"common-technical-translation-terminology-errors","status":"publish","type":"post","link":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/","title":{"rendered":"10 common technical translation terminology errors to fix"},"content":{"rendered":"<\/p>\n<p>The most frequent terminology failures in technical translation are wrong term selection, inconsistent term use across a document set, false friends, missing equivalents for new concepts, and terms lifted uncritically from machine translation output. Every one of these is preventable with the same first move: build a governed glossary or termbase before translation starts, and route anything safety-critical through subject-matter expert (SME) sign-off.<\/p>\n<p>That single step catches most of what goes wrong. The rest is discipline: enforcing the termbase inside your CAT tool, running consistency checks before delivery, and knowing when a document needs a NAATI-certified translator rather than a generalist.<\/p>\n<p>The categories worth watching for, in rough order of frequency:<\/p>\n<ul>\n<li>Wrong term selection (a plausible but incorrect synonym)<\/li>\n<li>Inconsistent terminology across the same document or product suite<\/li>\n<li>False friends (words that look equivalent but carry a different meaning)<\/li>\n<li>Missing equivalents for neologisms and newly coined technical terms<\/li>\n<li>Acronym and abbreviation mishandling<\/li>\n<li>Unit and measurement conversion mistakes<\/li>\n<li>Literal, word-for-word translation of idiomatic technical phrasing<\/li>\n<li>Terms carried over uncorrected from machine translation output<\/li>\n<li>Omissions and unauthorised additions<\/li>\n<li>Mismatched wording between UI labels and the documentation that describes them<\/li>\n<\/ul>\n<p>One <a href=\"https:\/\/doi.org\/10.5281\/zenodo.18080496\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">study on terminological accuracy in technical translation<\/a> singles out inconsistency, polysemy, and neologisms as the three recurring failure points, and recommends terminographic resources and unified terminology databases as the fix, not more careful individual translators. Safety and regulatory documents sit at the top of the risk list here: a wrong term in a marketing brochure is embarrassing, but a wrong term in a dosage instruction or a machine safety warning can hurt someone. Those documents need SME review and, in most cases, a certified translator, not just a good glossary.<\/p>\n<h2 id=\"key-takeaways\">Key Takeaways<\/h2>\n<p>Terminology errors are prevented by governing terms before translation starts, enforcing them through tooling during translation, and validating them with SMEs and certified translators wherever safety or regulatory risk is present.<\/p>\n<table>\n<thead>\n<tr>\n<th>Point<\/th>\n<th>Details<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Govern terms early<\/td>\n<td>Build and validate a glossary before translation begins, not after errors surface in review.<\/td>\n<\/tr>\n<tr>\n<td>Use TBX and a termbase<\/td>\n<td>Structure terminology data in a TBX-compliant termbase so it moves cleanly between tools and projects.<\/td>\n<\/tr>\n<tr>\n<td>Involve SMEs on risk items<\/td>\n<td>Route safety-critical and regulatory terms to a subject-matter expert for validation, not translator judgement alone.<\/td>\n<\/tr>\n<tr>\n<td>Enforce inside the CAT tool<\/td>\n<td>Configure your translation memory system to flag or block deviations from approved terms automatically.<\/td>\n<\/tr>\n<tr>\n<td>Choose Certitranslate for certified work<\/td>\n<td>Certitranslate\u2019s NAATI-certified translators handle technical documents with glossary export and SME-backed sign-off.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"table-of-contents\">Table of Contents<\/h2>\n<ul>\n<li><a href=\"#common-technical-translation-terminology-errors-ranked-by-frequency\">Common technical translation terminology errors ranked by frequency<\/a><\/li>\n<li><a href=\"#why-do-terminology-errors-keep-happening\">Why do terminology errors keep happening?<\/a><\/li>\n<li><a href=\"#how-to-avoid-translation-errors-a-priority-checklist\">How to avoid translation errors: a priority checklist<\/a><\/li>\n<li><a href=\"#what-tools-and-standards-actually-enforce-correct-terminology\">What tools and standards actually enforce correct terminology?<\/a><\/li>\n<li><a href=\"#a-qa-workflow-you-can-copy-for-terminology-checks\">A QA workflow you can copy for terminology checks<\/a><\/li>\n<li><a href=\"#when-does-a-document-need-a-certified-or-specialist-translator\">When does a document need a certified or specialist translator?<\/a><\/li>\n<li><a href=\"#what-ive-learned-watching-terminology-reviews-go-right-and-wrong\">What I\u2019ve learned watching terminology reviews go right and wrong<\/a><\/li>\n<li><a href=\"#sponsor-service-option-what-certified-technical-translation-delivers\">Sponsor \/ service option: what certified technical translation delivers<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently asked questions<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ul>\n<h2 id=\"common-technical-translation-terminology-errors-ranked-by-frequency\">Common technical translation terminology errors ranked by frequency<\/h2>\n<h3 id=\"1-wrong-term-selection\">1. Wrong term selection<\/h3>\n<p>This is the most common error and the hardest to spot without domain knowledge, because the mistranslation is a real word, just the wrong one for the context. A translator working from a general dictionary might render \u201crelease\u201d as a physical unlocking mechanism when the source text meant a software version. The consequence ranges from mild reader confusion to a support team fielding calls about a feature that \u201cdoesn\u2019t exist\u201d because it was labelled with the wrong term.<\/p>\n<h3 id=\"2-inconsistent-terminology-across-documents\">2. Inconsistent terminology across documents<\/h3>\n<p>The same source term gets three or four different translations across a manual, a UI, and a marketing page, often because different translators worked on each without a shared reference. Readers start doubting whether the different terms mean different things, which is worse than a single wrong translation because it erodes trust in the whole document set. This is also the easiest error to catch mechanically: a translation memory \u2122 search that returns more than two or three approved renderings of the same source term is a reliable red flag.<\/p>\n<h3 id=\"3-false-friends\">3. False friends<\/h3>\n<p>Words that look related across two languages but mean something different trip up even experienced translators, especially under deadline pressure. The classic example is a term that resembles an English cognate but denotes a different mechanism or process in the target language\u2019s technical register. In a safety manual, a false friend can flip an instruction\u2019s meaning entirely, turning \u201cdo not\u201d into an implied \u201cyou may\u201d if the negation or modal verb gets mistranslated alongside the term.<\/p>\n<h3 id=\"4-missing-equivalents-for-neologisms\">4. Missing equivalents for neologisms<\/h3>\n<p>Fast-moving fields coin new terms faster than dictionaries update, and a translator with no glossary access will often improvise a literal calque that nobody in the target market actually uses. The fix isn\u2019t guessing. It\u2019s flagging the term for SME input and adding it to the termbase once resolved, so the next translator on the project doesn\u2019t repeat the guess differently.<\/p>\n<h3 id=\"5-acronym-and-abbreviation-errors\">5. Acronym and abbreviation errors<\/h3>\n<p>Acronyms are dangerous because they often need to stay untranslated, get expanded on first use, or get replaced with a completely different target-language acronym, and the rule changes by document type and industry. Translating an acronym literally, letter by letter, can produce something meaningless or, worse, something that maps to an unrelated acronym already in use in that field.<\/p>\n<h3 id=\"6-unit-and-measurement-mistakes\">6. Unit and measurement mistakes<\/h3>\n<p>Errors here fall into two types: failing to convert units when the target market uses a different system, and converting correctly but rounding in a way that breaches a tolerance specified in the source document. In engineering and pharmaceutical documents, a rounding error in a dosage or a tolerance specification isn\u2019t a style issue. It\u2019s a compliance and safety issue that can trigger regulatory rejection or, in the worst case, patient harm.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/certitranslate.com\/wp-content\/uploads\/2026\/08\/1786675140578_Hands-measuring-metal-part-with-caliper.jpeg\" alt=\"Hands measuring metal part with caliper\"><\/p>\n<h3 id=\"7-literal-word-for-word-translation\">7. Literal, word-for-word translation<\/h3>\n<p>Technical writing often uses fixed idiomatic phrasing that reads naturally to a native technical reader but breaks completely when translated word for word. A phrase like \u201ctorque down to spec\u201d translated literally can produce something a target-language technician simply won\u2019t recognise as an instruction to tighten a fastener to a specified value.<\/p>\n<h3 id=\"8-terms-carried-over-uncorrected-from-machine-translation\">8. Terms carried over uncorrected from machine translation<\/h3>\n<p>Raw MT output is a useful draft, not a finished translation, and terminology is where it fails most visibly. A comparative evaluation of terminology handling in phrase-based statistical MT versus neural MT found that both systems introduce systematic terminology errors when there\u2019s no targeted term constraint in place, meaning the errors aren\u2019t random typos, they\u2019re consistent and repeatable across a document. Left uncorrected by a human reviewer, that consistency actually makes the error harder to spot, because it looks intentional.<\/p>\n<h3 id=\"9-omissions-and-unauthorised-additions\">9. Omissions and unauthorised additions<\/h3>\n<p>A translator under time pressure sometimes drops a qualifying clause (\u201conly when the system is offline\u201d) or adds a clarifying phrase that isn\u2019t in the source. Both change the legal or technical scope of the instruction, and both are notoriously hard to catch in a monolingual read-through of the target text alone.<\/p>\n<h3 id=\"10-ui-label-and-documentation-mismatch\">10. UI label and documentation mismatch<\/h3>\n<p>A button labelled \u201cSync\u201d in the interface gets translated one way for space reasons, then the manual describing that same button uses a different, longer translation because the documentation translator worked from a different glossary entry or none at all. <a href=\"https:\/\/www2.eecs.berkeley.edu\/Pubs\/TechRpts\/2026\/Archive\/EECS-2026-6.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Context-aware terminology guidance<\/a> treats this as a structural problem, not a carelessness problem: a short UI label and its expanded documentation description are different translation tasks that happen to share a source term, and glossary entries need to record which context each approved rendering belongs to.<\/p>\n<h2 id=\"why-do-terminology-errors-keep-happening\">Why do terminology errors keep happening?<\/h2>\n<p>Most terminology failures trace back to a handful of process gaps rather than translator skill. Knowing which one is at play tells you what to fix.<\/p>\n<p><strong>No glossary or termbase governance.<\/strong> If there\u2019s no single approved source of truth, every translator makes an independent judgement call, and independent judgement calls diverge. Red flag: a term search across your TM returns more than three distinct approved translations for what should be one concept.<\/p>\n<p><strong>Poor source-text context.<\/strong> A translator handed an isolated string with no screenshot, no surrounding paragraph, and no product access will guess, and guesses about polysemous technical terms are often wrong. Red flag: translators submitting the same clarification question about the same term more than once across a project.<\/p>\n<p><strong>Lack of SME access.<\/strong> When there\u2019s no engineer, pharmacist, or product manager to ask, ambiguous terms get resolved by whoever is fastest to answer, not whoever is right. Red flag: a term query sits unanswered for more than a day and the translator proceeds with a best guess anyway.<\/p>\n<p><strong>Tight deadlines and file chunking.<\/strong> Splitting a large document across several translators to hit a deadline multiplies the inconsistency risk described above, because nobody sees the whole picture. Red flag: a rush job with more than two translators and no shared termbase update cadence.<\/p>\n<p><strong>Over-reliance on raw MT.<\/strong> MT is fast, but it repeats its own terminology mistakes with total confidence, which is exactly the trap the PB-SMT\/NMT <a href=\"https:\/\/link.springer.com\/article\/10.1007\/s10590-020-09251-z\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">comparative study<\/a> documents. Red flag: post-editing turnaround times that are suspiciously close to plain reading speed, suggesting no real term verification happened.<\/p>\n<p><strong>Ambiguous source wording.<\/strong> Source documents written quickly, often by engineers who aren\u2019t professional writers, sometimes use inconsistent terminology themselves before translation even begins. Red flag: the same concept named three different ways in the source language, which guarantees at least that much divergence in the target.<\/p>\n<p><strong>Multiple translators without TM\/termbase enforcement.<\/strong> Even a good termbase does nothing if the CAT tool isn\u2019t configured to flag or block deviations from it. Red flag: repeated customer support tickets referencing confusion about a single named feature or component.<\/p>\n<p><strong>Pro Tip:<\/strong> <em>If you only have time to check one thing before a project starts, check whether more than three approved translations exist in the TM for any single core term. That number alone tells you whether your terminology governance is working or theatre.<\/em><\/p>\n<p><img decoding=\"async\" src=\"https:\/\/certitranslate.com\/wp-content\/uploads\/2026\/08\/1786675272485_Why-do-terminology-errors-keep-happening-overview-diagram.jpeg\" alt=\"Why do terminology errors keep happening? \u2014 overview diagram\"><\/p>\n<h2 id=\"how-to-avoid-translation-errors-a-priority-checklist\">How to avoid translation errors: a priority checklist<\/h2>\n<p>Fixing terminology issues works best as a sequence, not a scattered set of good habits. Here\u2019s the order that catches the most problems for the least effort:<\/p>\n<ol>\n<li><strong>Capture source terms in context.<\/strong> Pull candidate terms from the source document along with a screenshot, surrounding sentence, and, for UI strings, the character limit. Context captured now saves a query later.<\/li>\n<li><strong>Build the initial glossary.<\/strong> Draft target-language equivalents for every flagged term, even tentatively, so translators have something to react to rather than starting from nothing.<\/li>\n<li><strong>Route ambiguous terms to an SME for validation.<\/strong> Don\u2019t let a translator\u2019s best guess become the permanent record without someone who understands the product confirming it.<\/li>\n<li><strong>Import the validated glossary into a termbase.<\/strong> A TBX-compliant termbase structures the data so it can move between tools and projects without being retyped or reinterpreted.<\/li>\n<li><strong>Configure CAT tool enforcement.<\/strong> Set the translation memory system to flag or block any rendering that deviates from the approved termbase entry, rather than relying on translators to remember it.<\/li>\n<li><strong>Set MT and post-editing rules.<\/strong> If MT is part of the workflow, apply term constraints where the tool supports them and require a human terminology check on every MT-assisted segment, not a spot check.<\/li>\n<li><strong>Run QA checks before sign-off.<\/strong> Consistency scans, regex checks on unit formats, and a bilingual review pass catch what enforcement alone misses.<\/li>\n<li><strong>Schedule periodic glossary review.<\/strong> Revisit the termbase at least annually, and immediately after any product or regulatory change, because a glossary that doesn\u2019t move with the product quietly goes stale.<\/li>\n<\/ol>\n<p>Small teams can run most of this on a well-structured spreadsheet with clear SME contact points, as long as someone owns the update cadence. Enterprise localisation teams get more value from a TBX-compliant termbase tied into a full translation management system (TMS), with role-based permissions separating who can propose a term from who can approve it. Either way, the <a href=\"https:\/\/www.iso.org\/standard\/72308.html\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ISO guidance on translation-oriented terminography<\/a> is worth reading once, because it defines the actual tasks and roles involved in building a terminology collection properly, rather than leaving that structure to guesswork.<\/p>\n<p><strong>Pro Tip:<\/strong> <em>Add a \u201cforbidden terms\u201d field to every glossary entry, not just the approved translation. Recording what NOT to use is often more useful than recording what to use, because it stops a rejected term from resurfacing in the next project cycle.<\/em><\/p>\n<p><strong>Pro Tip:<\/strong> <em>Link every glossary entry to the function or behaviour the term describes, not just the label. A term tied to \u201cwhat this button does\u201d survives a UI redesign; a term tied only to the old label doesn\u2019t.<\/em><\/p>\n<p>Tie glossary maintenance to the product release cycle itself, not to a separate translation calendar. When a feature changes, the terminology review should be a required step in the release checklist, so the glossary updates the same week the product does, not months later when someone notices the documentation is wrong.<\/p>\n<h2 id=\"what-tools-and-standards-actually-enforce-correct-terminology\">What tools and standards actually enforce correct terminology?<\/h2>\n<p>Terminology governance depends on a small set of standards and tool categories doing their specific jobs well, rather than one tool doing everything.<\/p>\n<ul>\n<li><strong>Termbase\/TMS platforms<\/strong> hold the approved terms, definitions, and context notes, and export them in interoperable formats for use across projects.<\/li>\n<li><strong>CAT\/TM tools<\/strong> enforce preferred and forbidden terms at the point of translation, flagging deviations as the translator works.<\/li>\n<li><strong>QA tools<\/strong> run consistency and regex checks across a finished translation, catching unit-format errors and terminology drift a human read-through can miss.<\/li>\n<li><strong>Corpora and industry glossaries<\/strong> give translators a reference for how a term is actually used in the field, not just how a dictionary defines it.<\/li>\n<li><strong>MT systems with terminology constraints<\/strong> reduce, though don\u2019t eliminate, the systematic term errors that raw MT output tends to produce.<\/li>\n<\/ul>\n<p>The TBX (TermBase eXchange) standard is the one worth prioritising if you\u2019re choosing between formats, because it\u2019s built specifically so a termbase can move between tools without losing structure. Platforms like <a href=\"https:\/\/phrase.com\/blog\/posts\/technical-translation-definition-importance-and-challenges\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Phrase<\/a> illustrate how a modern TMS enforces preferred and forbidden terms directly inside the translation environment, which is the practical difference between a glossary that exists and a glossary that gets followed.<\/p>\n<table>\n<thead>\n<tr>\n<th>Category<\/th>\n<th>Primary role<\/th>\n<th>When to adopt it<\/th>\n<th>Integration notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>TBX (standard)<\/td>\n<td>Structures terminology data for interoperability between tools<\/td>\n<td>Adopt as soon as you have more than one tool or vendor in your workflow<\/td>\n<td>Confirm TBX import\/export support before committing to a termbase platform<\/td>\n<\/tr>\n<tr>\n<td>Termbase\/TMS<\/td>\n<td>Governs approved terms, context, and status across projects<\/td>\n<td>Adopt once a project involves more than one translator<\/td>\n<td>Check API access and data residency if working with Australia-based clients or authorities<\/td>\n<\/tr>\n<tr>\n<td>CAT tools<\/td>\n<td>Enforces preferred\/forbidden terms at the point of translation<\/td>\n<td>Adopt for any project with an existing termbase to enforce<\/td>\n<td>Confirm the tool can flag, not just suggest, deviations from approved terms<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If you\u2019re evaluating SaaS tools for an Australia-facing workflow, check data residency terms, TBX import and export support, and whether the platform offers API access for tying the termbase into your existing content pipeline. None of that is exotic. It\u2019s just easy to skip when a tool\u2019s marketing page leads with features instead of compliance basics.<\/p>\n<h2 id=\"a-qa-workflow-you-can-copy-for-terminology-checks\">A QA workflow you can copy for terminology checks<\/h2>\n<p>Run terminology QA in three stages, not as a single pass at the end.<\/p>\n<p><strong>Pre-translation:<\/strong> extract candidate terms from the source document, request SME access before translation starts (not after a query comes up), and seed the glossary with tentative renderings so translators have a starting reference.<\/p>\n<p><strong>During translation:<\/strong> enforce the termbase inside the CAT tool, apply MT term filters where MT is used, and route ambiguous terms as inline queries rather than silent guesses.<\/p>\n<p><strong>Post-translation:<\/strong> run a bilingual revision pass, get SME validation on any flagged term, run automated QA checks, and require a final sign-off before delivery.<\/p>\n<p>Two QA checks worth running on every technical project:<\/p>\n<ol>\n<li>Search the TM for any source term with more than two approved alternate translations, and resolve the divergence before delivery.<\/li>\n<li>Run a regex check across the target text for unit and measurement formats, catching conversion or rounding errors that a visual read-through often misses.<\/li>\n<\/ol>\n<p>A reusable term query to an SME should include four fields: the term itself, the surrounding context or sentence, a screenshot if it\u2019s a UI element, and two or three proposed translation options for the SME to choose between or correct. That last field matters more than people expect. It\u2019s much faster for an SME to pick between three options than to generate one from scratch.<\/p>\n<p>At sign-off, request three artefacts from your reviewer: a glossary export in TBX or CSV format, written reviewer notes on anything ambiguous, and an explicit SME approval stamp on any safety-critical term. A glossary maintenance guide for engineering and manufacturing teams recommends reviewing the full glossary at least annually, which is a reasonable floor even for teams that update more frequently around major releases.<\/p>\n<h2 id=\"when-does-a-document-need-a-certified-or-specialist-translator\">When does a document need a certified or specialist translator?<\/h2>\n<p>Some documents carry legal or regulatory weight that makes a generalist translation, however competent, insufficient. These use-cases call for a certified or specialist translator as a baseline requirement, not an upgrade:<\/p>\n<ul>\n<li>Regulatory submissions to a government body or standards authority<\/li>\n<li>Medical device instructions and patient-facing safety information<\/li>\n<li>Safety-critical manuals for machinery, vehicles, or industrial equipment<\/li>\n<li>Patent filings, where a single mistranslated claim term can affect enforceability<\/li>\n<li>Legal-technical contracts that combine legal language with technical specification<\/li>\n<\/ul>\n<p>When commissioning a translation for any of these, request a specific set of deliverables upfront: a certified translation statement where the receiving authority requires one, a glossary or termbase export, SME review notes documenting how ambiguous terms were resolved, and a revision history showing what changed between drafts.<\/p>\n<p>In Australia, NAATI certification is the relevant credential for official submissions, and many government bodies, universities, and courts specifically require NAATI-certified translation before they\u2019ll accept a document. That\u2019s a procedural fact, not a sales pitch: if a document is going to an Australian authority, checking whether NAATI certification is required is one of the first questions to answer, not a detail to sort out later.<\/p>\n<table>\n<thead>\n<tr>\n<th>Point<\/th>\n<th>Details<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Certification requirement<\/td>\n<td>Confirm whether the receiving authority requires a NAATI-certified translator before commissioning the work.<\/td>\n<\/tr>\n<tr>\n<td>Deliverables to request<\/td>\n<td>Certified statement, glossary\/termbase export, SME review notes, and a revision history.<\/td>\n<\/tr>\n<tr>\n<td>Highest-risk documents<\/td>\n<td>Medical, safety, patent, and regulatory documents need specialist review, not just a fluent translator.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"what-ive-learned-watching-terminology-reviews-go-right-and-wrong\">What I\u2019ve learned watching terminology reviews go right and wrong<\/h2>\n<p>The projects that go smoothly almost always share one trait: someone brought the subject-matter expert in during the glossary build, not after the first draft was already flagged for errors. I\u2019ve seen a release genuinely saved by a ten-minute conversation with an engineer who caught that a translated safety term implied the opposite instruction to the source, a mistake that would have shipped otherwise because it read perfectly naturally in the target language. That\u2019s the part generic terminology advice tends to underplay: an SME query isn\u2019t a delay, it\u2019s the cheapest insurance a technical translation project has.<\/p>\n<p>The cultural fix that actually sticks is a small one. Make a terminology review a gated step in the content release checklist, the same way a security review or a legal sign-off is gated. Not a suggestion, not a \u201cnice to have if there\u2019s time.\u201d If terminology approval can\u2019t be skipped without someone actively overriding it, it stops being the thing that quietly gets dropped under deadline pressure.<\/p>\n<h2 id=\"sponsor-service-option-what-certified-technical-translation-delivers\">Sponsor \/ service option: what certified technical translation delivers<\/h2>\n<p>There are ways to manage terminology in-house with a spreadsheet and a patient SME, and for a lot of internal documentation, that\u2019s a perfectly reasonable path. But when a document is going to a regulator, a court, or an overseas authority, the calculation changes: you need someone who can put their name and credentials behind the accuracy of every term, not just a careful reviewer.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/certitranslate.com\/wp-content\/uploads\/2026\/08\/1781637786858_certitranslate.jpg\" alt=\"Certitranslate\"><\/p>\n<p>Certitranslate works with NAATI-certified translators who handle technical documents with the same terminology discipline outlined above, built into the process rather than bolted on afterwards. A typical engagement includes the translation itself, a certified statement where the receiving authority requires one, a glossary or termbase export in TBX or CSV format, and reviewer notes documenting how any ambiguous terms were resolved. That last part matters if the document ever needs revision or gets challenged, because the resolution is on record, not buried in someone\u2019s inbox.<\/p>\n<p>If you\u2019re commissioning a manual, safety document, or regulatory submission and need those deliverables done properly, the <a href=\"https:\/\/certitranslate.com\/es\/technical-manual-translation-step-by-step\/\" target=\"_blank\" rel=\"noopener\">technical manual translation guide<\/a> walks through what to expect, and you can get a quote through Certitranslate\u2019s <a href=\"https:\/\/certitranslate.com\/es\/services\/technical-translation\/\" target=\"_blank\" rel=\"noopener\">technical translation service<\/a> page to see turnaround and scope for your specific document.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently asked questions<\/h2>\n<p><strong>What is the most common terminology error in technical translation?<\/strong><br \/>\nWrong term selection ranks highest, because the translated word is real and plausible, just incorrect for that specific technical context, which makes it harder to catch than an obvious mistranslation.<\/p>\n<p><strong>How do I stop machine translation from introducing terminology errors?<\/strong><br \/>\nApply term constraints where your MT tool supports them, and require a human reviewer to check every MT-assisted segment against your approved glossary rather than spot-checking a sample.<\/p>\n<p><strong>Do I need a NAATI-certified translator for a technical manual?<\/strong><br \/>\nOnly if the manual is being submitted to an authority that requires certification, but safety-critical manuals and anything headed to a regulator should default to certified or specialist review regardless.<\/p>\n<p><strong>How often should a technical glossary be reviewed?<\/strong><br \/>\nAt least annually, and immediately after any product feature change or regulatory update that affects the terms already in the glossary.<\/p>\n<p><strong>What\u2019s the difference between a termbase and a glossary?<\/strong><br \/>\nA glossary is typically a simpler list of approved terms and translations, while a termbase is a structured, often TBX-compliant database that records context, status, and review history for each entry, and integrates directly with CAT tools.<\/p>\n<h2 id=\"sources\">Sources<\/h2>\n<ul>\n<li><a href=\"https:\/\/doi.org\/10.5281\/zenodo.18080496\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">TERMINOLOGICAL ACCURACY AS A KEY FACTOR IN TRANSLATING TECHNICAL TEXTS: PROBLEMS AND SOLUTIONS<\/a><\/li>\n<li><a href=\"https:\/\/www.iso.org\/standard\/72308.html\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">ISO 72308 \u2014 Translation-oriented terminography: requirements and recommendations<\/a><\/li>\n<li><a href=\"https:\/\/phrase.com\/blog\/posts\/technical-translation-definition-importance-and-challenges\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Technical Translation: Definition, Examples, Best Practices | Phrase<\/a><\/li>\n<li><a href=\"https:\/\/www2.eecs.berkeley.edu\/Pubs\/TechRpts\/2026\/Archive\/EECS-2026-6.pdf\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">Context-aware terminology strategies for UI and documentation \u2014 EECS technical report<\/a><\/li>\n<\/ul>\n<h2 id=\"recommended\">Recommended<\/h2>\n<ul>\n<li><a href=\"https:\/\/certitranslate.com\/es\/what-is-technical-terminology-accuracy\/\" target=\"_blank\" rel=\"noopener\">Technical terminology accuracy: what it means and why it matters &#8211; CertiTranslate &#8211; Translations by NAATI Certified Translators<\/a><\/li>\n<li><a href=\"https:\/\/certitranslate.com\/es\/technical-manual-translation-step-by-step\/\" target=\"_blank\" rel=\"noopener\">Technical manual translation step by step: a guide for professionals &#8211; CertiTranslate &#8211; Translations by NAATI Certified Translators<\/a><\/li>\n<li><a href=\"https:\/\/certitranslate.com\/es\/top-7-mistakes-to-avoid-when-submitting-translated-documents-to-australian-authorities\/\" target=\"_blank\" rel=\"noopener\">Top 7 Mistakes to Avoid When Submitting Translated Documents &#8211; CertiTranslate &#8211; Translations by NAATI Certified Translators<\/a><\/li>\n<li><a href=\"https:\/\/certitranslate.com\/es\/why-legal-terminology-requires-a-specialist-translator\/\" target=\"_blank\" rel=\"noopener\">Why legal terminology requires a specialist translator &#8211; CertiTranslate &#8211; Translations by NAATI Certified Translators<\/a><\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"<p>Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.<\/p>","protected":false},"author":1,"featured_media":10711,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10710","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"admin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"es_ES\" \/>\n\t\t<meta property=\"og:site_name\" content=\"CertiTranslate - Translations by NAATI Certified Translators -\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"10 common technical translation terminology errors to fix\" \/>\n\t\t<meta property=\"og:description\" content=\"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-08-17T02:00:21+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-09-04T12:42:09+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"10 common technical translation terminology errors to fix\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#blogposting\",\"name\":\"10 common technical translation terminology errors to fix\",\"headline\":\"10 common technical translation terminology errors to fix\",\"description\":\"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.\",\"author\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/author\\\/admin_0nvps2z1\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/1786675133627_Translator-checking-glossary-on-tablet.jpeg\",\"width\":1260,\"height\":720,\"caption\":\"Translator checking glossary on tablet\"},\"datePublished\":\"2026-08-17T02:00:21+00:00\",\"dateModified\":\"2026-09-04T12:42:09+00:00\",\"inLanguage\":\"es-ES\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#webpage\"},\"articleSection\":\"Uncategorized\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/certitranslate.com\\\/es\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/category\\\/uncategorized\\\/#listItem\",\"name\":\"Uncategorized\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/category\\\/uncategorized\\\/#listItem\",\"position\":2,\"name\":\"Uncategorized\",\"item\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/category\\\/uncategorized\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#listItem\",\"name\":\"10 common technical translation terminology errors to fix\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#listItem\",\"position\":3,\"name\":\"10 common technical translation terminology errors to fix\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/category\\\/uncategorized\\\/#listItem\",\"name\":\"Uncategorized\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/#organization\",\"name\":\"CertiTranslate - Translations by NAATI Certified Translators\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/author\\\/admin_0nvps2z1\\\/#author\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/author\\\/admin_0nvps2z1\\\/\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1cfd204148d0e80afd5a16c985be38dc9b8243255d0e29fcc00a4823e99bc1d4?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"admin\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#webpage\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/\",\"name\":\"10 common technical translation terminology errors to fix\",\"description\":\"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.\",\"inLanguage\":\"es-ES\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/author\\\/admin_0nvps2z1\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/author\\\/admin_0nvps2z1\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/1786675133627_Translator-checking-glossary-on-tablet.jpeg\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#mainImage\",\"width\":1260,\"height\":720,\"caption\":\"Translator checking glossary on tablet\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/blog\\\/common-technical-translation-terminology-errors\\\/#mainImage\"},\"datePublished\":\"2026-08-17T02:00:21+00:00\",\"dateModified\":\"2026-09-04T12:42:09+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/#website\",\"url\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/\",\"name\":\"CertiTranslate - Translations by NAATI Certified Translators\",\"inLanguage\":\"es-ES\",\"publisher\":{\"@id\":\"https:\\\/\\\/certitranslate.com\\\/es\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"10 common technical translation terminology errors to fix","description":"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.","canonical_url":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#blogposting","name":"10 common technical translation terminology errors to fix","headline":"10 common technical translation terminology errors to fix","description":"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.","author":{"@id":"https:\/\/certitranslate.com\/es\/blog\/author\/admin_0nvps2z1\/#author"},"publisher":{"@id":"https:\/\/certitranslate.com\/es\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/certitranslate.com\/wp-content\/uploads\/2026\/08\/1786675133627_Translator-checking-glossary-on-tablet.jpeg","width":1260,"height":720,"caption":"Translator checking glossary on tablet"},"datePublished":"2026-08-17T02:00:21+00:00","dateModified":"2026-09-04T12:42:09+00:00","inLanguage":"es-ES","mainEntityOfPage":{"@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#webpage"},"isPartOf":{"@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#webpage"},"articleSection":"Uncategorized"},{"@type":"BreadcrumbList","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es#listItem","position":1,"name":"Home","item":"https:\/\/certitranslate.com\/es","nextItem":{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/#listItem","name":"Uncategorized"}},{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/#listItem","position":2,"name":"Uncategorized","item":"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/","nextItem":{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#listItem","name":"10 common technical translation terminology errors to fix"},"previousItem":{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#listItem","position":3,"name":"10 common technical translation terminology errors to fix","previousItem":{"@type":"ListItem","@id":"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/#listItem","name":"Uncategorized"}}]},{"@type":"Organization","@id":"https:\/\/certitranslate.com\/es\/#organization","name":"CertiTranslate - Translations by NAATI Certified Translators","url":"https:\/\/certitranslate.com\/es\/"},{"@type":"Person","@id":"https:\/\/certitranslate.com\/es\/blog\/author\/admin_0nvps2z1\/#author","url":"https:\/\/certitranslate.com\/es\/blog\/author\/admin_0nvps2z1\/","name":"admin","image":{"@type":"ImageObject","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/1cfd204148d0e80afd5a16c985be38dc9b8243255d0e29fcc00a4823e99bc1d4?s=96&d=mm&r=g","width":96,"height":96,"caption":"admin"}},{"@type":"WebPage","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#webpage","url":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/","name":"10 common technical translation terminology errors to fix","description":"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.","inLanguage":"es-ES","isPartOf":{"@id":"https:\/\/certitranslate.com\/es\/#website"},"breadcrumb":{"@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#breadcrumblist"},"author":{"@id":"https:\/\/certitranslate.com\/es\/blog\/author\/admin_0nvps2z1\/#author"},"creator":{"@id":"https:\/\/certitranslate.com\/es\/blog\/author\/admin_0nvps2z1\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/certitranslate.com\/wp-content\/uploads\/2026\/08\/1786675133627_Translator-checking-glossary-on-tablet.jpeg","@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#mainImage","width":1260,"height":720,"caption":"Translator checking glossary on tablet"},"primaryImageOfPage":{"@id":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/#mainImage"},"datePublished":"2026-08-17T02:00:21+00:00","dateModified":"2026-09-04T12:42:09+00:00"},{"@type":"WebSite","@id":"https:\/\/certitranslate.com\/es\/#website","url":"https:\/\/certitranslate.com\/es\/","name":"CertiTranslate - Translations by NAATI Certified Translators","inLanguage":"es-ES","publisher":{"@id":"https:\/\/certitranslate.com\/es\/#organization"}}]},"og:locale":"es_ES","og:site_name":"CertiTranslate - Translations by NAATI Certified Translators -","og:type":"article","og:title":"10 common technical translation terminology errors to fix","og:description":"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission.","og:url":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/","article:published_time":"2026-08-17T02:00:21+00:00","article:modified_time":"2026-09-04T12:42:09+00:00","twitter:card":"summary_large_image","twitter:title":"10 common technical translation terminology errors to fix","twitter:description":"Review ten common technical translation terminology errors, how they affect accuracy and compliance, and the steps to correct each issue before submission."},"aioseo_meta_data":{"post_id":"10710","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":null,"created":"2026-08-17 02:01:24","updated":"2026-09-04 23:04:51","seo_analyzer_scan_date":null,"focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/certitranslate.com\/es\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/\" title=\"Uncategorized\">Uncategorized<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t10 common technical translation terminology errors to fix\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/certitranslate.com\/es"},{"label":"Uncategorized","link":"https:\/\/certitranslate.com\/es\/blog\/category\/uncategorized\/"},{"label":"10 common technical translation terminology errors to fix","link":"https:\/\/certitranslate.com\/es\/blog\/common-technical-translation-terminology-errors\/"}],"_links":{"self":[{"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/posts\/10710","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/comments?post=10710"}],"version-history":[{"count":2,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/posts\/10710\/revisions"}],"predecessor-version":[{"id":10854,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/posts\/10710\/revisions\/10854"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/media\/10711"}],"wp:attachment":[{"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/media?parent=10710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/categories?post=10710"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/certitranslate.com\/es\/wp-json\/wp\/v2\/tags?post=10710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}