🐭 Docs: Fix admonition syntax and typo

Three `!!!note` admonitions in `dev-standards.md` were missing the required space before
the type keyword, causing MkDocs to render them as plain text instead of styled
callouts. Also fix a "the" → "then" typo in `developer.md`.

Author: mbercx

docs/dev-standards.md

@@ -5,7 +5,7 @@ Good development standards make for better code.
 
 **Versioning**: We try to adhere to [SemVer](https://semver.org/).
 
-!!!note
+!!! note
 
     The stipulations below are based on experience, but are still evolving.
     This text is mainly here to provide a starting point for discussion with collaborators.
@@ -103,14 +103,14 @@ Similarly, if a dependency is changed, it's convenient to quickly spot this, e.g
 | 🐭    | minor changes (typos etc.; exclude from changelog)               | `chore`                                   | No                        |
 | ❓    | anything not covered above (last resort)                         | `chore`                                   | No                        |
 
-!!!note
+!!! note
 
     We are aware of other standards like [GitMoji](https://gitmoji.dev/), but limit the number in order to avoid choice overload.
     Too many options make it difficult for contributors to know all of them, makes changelogs too fragmented and leads to decision paralysis.
     Moreover, we avoid emojis that typically have width issues in some terminals.
     <!-- TODO: Also look into and add reference to https://github.com/ahmadawais/Emoji-Log -->
 
-!!!note
+!!! note
 
     Not everyone likes emojis. In the dropdown below you can find some common concerns.
 

docs/developer.md

@@ -51,4 +51,4 @@ And then push the tag to the remote, here named `origin`:
 
     git push origin --tags
 
-You can the go to the [Github releases](https://github.com/mbercx/python-copier/releases) and make a new release based on the new tag.
+You can then go to the [Github releases](https://github.com/mbercx/python-copier/releases) and make a new release based on the new tag.