> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/docx-editor.md). # DOCX Editor - [Apryse DOCX Editor Overview](https://docs.apryse.com/web/docx-editor/docx-editor.md): Embed native Word editing into your app with Apryse DOCX Editor—part of the Web SDK Office suite. Supports JavaScript frameworks like React, Angular, Vue, Nuxt.js, or Next.js. - [Enable Apryse DOCX Editor](https://docs.apryse.com/web/docx-editor/edit-docx-file.md): Create and edit DOCX files in JavaScript with Apryse WebViewer. Get started by integrating the DOCX Editor and rendering Word documents directly in your web app. - [Format text with DOCX Editor](https://docs.apryse.com/web/docx-editor/format-text.md): Learn how to apply bold, italic, underline, font color, and highlighting to text in the WebViewer DOCX Editor, using the UI or programmatically. - [Track changes with Apryse DOCX Editor](https://docs.apryse.com/web/docx-editor/docx-editor-tracked-changes.md): Learn how to implement track changes in the Apryse DOCX Editor using a JavaScript API. Retrieve, navigate, and manage tracked changes with events and UI controls. - [Set initial edit mode in Apryse DOCX Editor](https://docs.apryse.com/web/docx-editor/docx-editor-initial-edit-mode.md): Learn how to set the initial edit mode in the Apryse DOCX Editor using WebViewer and JavaScript. Control editing behavior when documents first load. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.apryse.com/web/docx-editor.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.