> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/smart-templates/faq/why-are-some-buttons-in-the-q-and-a-shown-in-the-wrong-language.md). # Why are some buttons in the Q\&A shown in the wrong language? When you upload a Word document to create a Smart Template, Clausebuddy will detect the language of the document. This language will be set as the underlying language of the Q\&A. While you write the questions to be featured in the Q\&A yourself (and thus determine the language used), some fixed buttons and drop down menus will feature default wording (for example, 'Add additional answers'). This default text will always appear in the language as determined by Clausebuddy on the basis of the uploaded underlying Word document. If Clausebuddy has misjudged this language or when you have created a duplicate of a Q\&A to create another language version, the default text in the buttons and drop-down menus may appear in the wrong language.\ We are considering giving the end-user in the future the option to change the underlying language. However, at this moment, there is no such option yet as we did not want to make the Smart Template module too complex. If you experience this issue and want to have the underlying language of the Q\&A changed, please send us a short message to our support team at: --- # 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://help.clausebuddy.com/smart-templates/faq/why-are-some-buttons-in-the-q-and-a-shown-in-the-wrong-language.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.