docs(almalinux): fix requirements to deploy

fixes #213

#<optional body>
#
#<optional footer>
#
# TYPES
#   API relevant changes
#     feat: Commits, that adds or remove a new feature
#     fix: Commits, that fixes a bug
#   refactor: Commits, that rewrite/restructure your code, however does not change any API behaviour
#     perf: Commits are special refactor commits, that improve performance
#   style: Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
#   test: Commits, that add missing tests or correcting existing tests
#   docs: Commits, that affect documentation only
#   build: Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ...
#   ops: Commits, that affect operational components like infrastructure, deployment, backup, recovery, ...
#   chore: Miscellaneous commits e.g. modifying .gitignore
#
# Description
# The description contains a concise description of the change.
# Use the imperative, present tense: "change" not "changed" nor "changes"
# Think of This commit will... or This commit should...
# Don't capitalize the first letter
# No dot (.) at the end
#
# Body
# The body should include the motivation for the change and contrast this with previous behavior.
# Use the imperative, present tense: "change" not "changed" nor "changes"
# This is the place to mention issue identifiers and their relations
#
# Footer
# The footer should contain any information about Breaking Changes and is also the place to reference Issues that this commit refers to.
# optionally reference an issue by its id.
# Breaking Changes should start with the word BREAKING CHANGES: followed by space or two newlines. The rest of the commit message is then used for this.

alma8/README.md

@@ -12,8 +12,8 @@ The Packer template in this directory creates a Alma 8 AMD64 image for use with
 
 ## Requirements to deploy the image
 
-* [MAAS](https://maas.io) 3.3 or later, as that version introduces support for Alma
-* [Curtin](https://launchpad.net/curtin) 22.1. If you have a MAAS with an earlier Curtin version, you can [patch](https://code.launchpad.net/~xnox/curtin/+git/curtin/+merge/415604) distro.py to deploy Alma.
+* [MAAS](https://maas.io) 3.5 or later, as that version introduces support for Alma
+* [Curtin](https://launchpad.net/curtin) 23.1 or later. If you have a MAAS with an earlier Curtin version, you can [patch](https://code.launchpad.net/~alexsander-souza/curtin/+git/curtin/+merge/462367) distro.py to deploy Alma.
 
 ## Customizing the image
 

alma9/README.md

@@ -12,8 +12,8 @@ The Packer template in this directory creates a Alma 9 AMD64 image for use with
 
 ## Requirements to deploy the image
 
-* [MAAS](https://maas.io) 3.3 or later, as that version introduces support for Alma
-* [Curtin](https://launchpad.net/curtin) >22.1
+* [MAAS](https://maas.io) 3.5 or later, as that version introduces support for Alma
+* [Curtin](https://launchpad.net/curtin) 23.1 or later. If you have a MAAS with an earlier Curtin version, you can [patch](https://code.launchpad.net/~alexsander-souza/curtin/+git/curtin/+merge/462367) distro.py to deploy Alma.
 
 ## Customizing the image