> For the complete documentation index, see [llms.txt](https://medievalbook.gitbook.io/digitizing-medieval-archives/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://medievalbook.gitbook.io/digitizing-medieval-archives/week-7.md). # Week 7 - Abbreviations ### Abbreviations This week is all about unpacking abbreviations and understanding how the medieval abbreviation system works. You will have installed a medieval-abbreviation based unicode onto your system already so you're getting a look at what the medieval abbreviation system looks like. The readings, however, explain the logic of the system and try to help explain what they were thinking. We also use loads of abbreviations and acronyms in our everyday life - in official discourse (e.g. PMO = Prime Minster's Office) or casual texting. Before we even want to start with medieval abbreviations, let's think about what abbreviations YOU use regularly everyday. We're going to make a list... ### --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://medievalbook.gitbook.io/digitizing-medieval-archives/week-7.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.