From cb8fdd0da7320d5655eadb8b293760c42c5c1661 Mon Sep 17 00:00:00 2001
From: Joost van den Born <48867822+yosata@users.noreply.github.com>
Date: Wed, 12 May 2021 09:31:53 +0200
Subject: [PATCH] Update README.md

Fixed a typo in the markdown formatting
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index cb5427d..26a0ddd 100644
--- a/README.md
+++ b/README.md
@@ -23,12 +23,12 @@ footers and headers as closely as possible.
   They receive the appropriate label ([AD...] and [RD...]) and are placed in separate reference tables. All references in the `ApplicableDocuments.bib` file are
   printed in the Applicable Documents table, but only the reference documents that are cited in text are printed in the Reference Documents table.
 - Fill the change record table in the document pre-amble. Depending on the document type, the location of the Change Record table might change.
-- Many acronyms used in MICADO documentation are already included in the `acronyms.tex` file. Use in the text with `\ac{}`, `\acs{}` or \acl{}.
+- Many acronyms used in MICADO documentation are already included in the `acronyms.tex` file. Use in the text with `\ac{}`, `\acs{}` or `\acl{}`.
 - Nested acronyms are possible. Both will be printed in the acronym list. For example, MICADO - The Multi-AO Imaging CamerA for Deep Observations - uses AO in the
   long version. Therefore, AO - Adaptive Optics - will also be printed in the acronyms list.
 - Extensive comments explaining what is what in the `.tex` and `.sty` files.
 
-## Minimal Working Example
+## An example document
 Please, check the provided example PDFs to get a feel for what the document types might look like.
 
 ```