[doc] Fix typos, spelling mistakes, and grammar issues across docs/ folder

[Copilot]

Comprehensive cleanup of ~70+ documentation errors across 19 files, catalogued in the linked issue. Covers spelling typos, subject-verb agreement, wrong verb forms, missing plurals, and article misuse.

Changes by category

Recurring patterns fixed across multiple files:

• previzualize → preview (×14 across exploring-*.md files)
• a markdown files → a markdown file (×9)
• an other Organization → another Organization (×multiple)
• supportss / supportsing → supports / supporting (×8 in automation.md)
• an analytic report → an analytical report

File-specific fixes:

• automation.md: cliking → clicking, Specifities → Specificities, triggering yur → triggering your, umatch/unmatch → unmatched, processess → processes, will follow will follow → will follow, Asignee → Assignee, troublshooting → troubleshooting, mutliple → multiple
• exploring-arsenal.md: Two section headings incorrectly read "Visualizing Knowledge associated with an Observed Data" — corrected to reference the actual entity (Tool / Vulnerability)
• authentication.md: Entreprise → Enterprise, OpenCTI use/support → uses/supports
• nested.md: defintions → definitions ×2, modelized → modeled
• case-management.md: modelize → modeled, oversaw → overseen, transfered → transferred, immediatly → immediately, meaningfull → meaningful
• exploring-analysis.md: reseearch → research, payed → paid, serie → series, depending of → depending on, reasonging → reasoning, malicioussness → maliciousness
• deduplication.md: criterias → criteria
• refine-content.md: imbrication → nesting, tha → the
• search.md: accross → across, an case-insensitive → a case-insensitive, capabilities is available → capability is available
• notifiers.md: security reason → security reasons, you extends → you extend
• widgets.md: Missing space — configuration.Therefore → configuration. Therefore
• pivoting.md: Wehn → When, doted → dotted
• python.md: plaform → platform
• getting-started.md: Stray whitespace before period in table cell

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Docs] Typos, spelling mistakes, and grammar issues across the docs/ folder</issue_title>
<issue_description>## Description

A comprehensive review of the docs/ folder revealed numerous typos, spelling mistakes, and grammar issues across multiple files. This issue catalogs all findings to facilitate a cleanup PR.

---

Findings by file

docs/docs/development/python.md

Line/Context	Issue	Suggested Fix
"interact with the openCTI plaform"	Typo: "plaform"	→ "platform"

---

docs/docs/deployment/authentication.md

Line/Context	Issue	Suggested Fix
"is an Entreprise Edition feature"	Typo: "Entreprise"	→ "Enterprise"
"OpenCTI use this strategy"	Subject-verb agreement	→ "OpenCTI uses this strategy"
"nested reference to multiple marking defintions" (in nested.md, referenced in SAML JSON comments)	Typo: "defintions"	→ "definitions"
"OpenCTI support mapping OpenID Claims"	Subject-verb agreement	→ "OpenCTI supports mapping"
"OpenCTI support mapping SAML Roles/Groups"	Subject-verb agreement	→ "OpenCTI supports mapping"

---

docs/docs/usage/nested.md

Line/Context	Issue	Suggested Fix
"Refer to other objects in directly in their attributes"	Extra word "in"	→ "Refer to other objects directly in their attributes"
"nested reference to multiple marking defintions" (×2 occurrences in code comments)	Typo: "defintions"	→ "definitions"
"all nested references and objects are modelized as relationships"	Non-standard word "modelized"	→ "modeled"

---

docs/docs/usage/case-management.md

Line/Context	Issue	Suggested Fix
"Multiple situations can be modelize in OpenCTI"	Verb form error: "modelize"	→ "modeled"
"and oversaw"	Wrong tense	→ "and overseen"
"your company has its own documents' templates, right?"	Informal tone; also odd possessive	Consider: "your company has its own document templates"
"a more meaningfull Timeline view"	Typo: "meaningfull"	→ "meaningful"
"has been transfered to OpenCTI"	Typo: "transfered"	→ "transferred"
"you are alerted immediatly"	Typo: "immediatly"	→ "immediately"
"trace all the work that have been done"	Grammar: subject-verb agreement	→ "trace all the work that has been done"

---

docs/docs/usage/exploring-analysis.md

Line/Context	Issue	Suggested Fix
"a security reseearch team"	Typo: "reseearch"	→ "research"
"the analyst payed attention"	Wrong past tense: "payed"	→ "paid"
"you will find a serie of icons"	Typo: "serie"	→ "series"
"Nodes are colored depending of their type"	Grammar: wrong preposition	→ "depending on their type"
"share your Report and its content with users of an other Organization"	Should be one word	→ "another"
"It also display if the SDO has been added directly or through inferences with the reasonging engine" (×2 in Groupings section)	Typo: "reasonging" + "display"	→ "reasoning" and "displays"
"how the analysis have been performed"	Grammar	→ "how the analysis has been performed"
"the malicioussness of the analysed artifact"	Typo: "malicioussness"	→ "maliciousness"
"This specific tab allows to previzualize" (×multiple occurrences across files)	Typo: "previzualize"	→ "preview" or "pre-visualize"
"a markdown files to feed a collaborative wiki with" (×multiple)	Grammar: "a...files"	→ "a markdown file" or "markdown files"
"an analytic report to share with other teams"	Should be "analytical"	→ "an analytical report" (or keep as stylistic choice)
"a External references is defined as such"	Grammar: article	→ "an External Reference is defined as such"

---

docs/docs/usage/exploring-entities.md

Line/Context	Issue	Suggested Fix
"OpenCTI's Entities objects provides"	Subject-verb agreement	→ "OpenCTI's Entity objects provide"
"This specific tab allows to previzualize" (×5 occurrences)	Typo: "previzualize"	→ "preview"
"a markdown files to feed a collaborative wiki with" (×5)	Grammar	→ "markdown files" or "a markdown file"

---

docs/docs/usage/exploring-arsenal.md

Line/Context	Issue	Suggested Fix
"Vulnerabilities are weaknesses or that can be exploited"	Incomplete sentence / extra "or"	→ "Vulnerabilities are weaknesses that can be exploited"
"Visualizing Knowledge associated with an Observed Data" (×2, for Tools and Vulnerabilities sections)	Wrong heading — should reference the actual entity	→ "...associated with a Tool" / "...associated with a Vulnerability"
`"This specific tab allows to pr...

• Fixes [Docs] Typos, spelling mistakes, and grammar issues across the docs/ folder #14620

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[github-actions]

Thank you for your contribution, but we need you to sign your commits. Please see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[github-actions]

Thank you for your contribution, but we need you to sign your commits. Please see https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.37%. Comparing base (0a6e615) to head (e55eb9c).
⚠️ Report is 65 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #14627   +/-   ##
=======================================
  Coverage   32.36%   32.37%           
=======================================
  Files        3096     3096           
  Lines      210896   210896           
  Branches    38197    38205    +8     
=======================================
+ Hits        68262    68281   +19     
+ Misses     142634   142615   -19     

Flag	Coverage Δ
opencti-client-python	45.50% <ø> (ø)
opencti-front	2.83% <ø> (ø)
opencti-graphql	67.76% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.