Update docs/turnkey-solution/hardware-landscape.md

Co-authored-by: Felix Kronlage-Dammers <[email protected]>
Signed-off-by: Marc Schöchlin <[email protected]>

Author: scoopex

docs/turnkey-solution/hardware-landscape.md

@@ -70,7 +70,7 @@ The relevant **References** section refers here to the individual documentation
 * Almost all installation steps are [documented and automated](https://github.com/SovereignCloudStack/hardware-landscape/blob/main/documentation/System_Deployment.md)
   based on a pure rack installation (The setup is extensively documented, in particular the few manual steps)
   * The entire customized setup of the nodes is [implemented by OSISM/Ansible](https://github.com/SovereignCloudStack/hardware-landscape/tree/main/environments/custom)
-  * All secrets (e.g. passwords) of the environment are stored and versioned in the encrypted Ansible Vault in i
+  * All secrets (e.g. passwords) of the environment are stored and versioned in the encrypted Ansible Vault in 
     the repository (when access is transferred, rekeying can be used to change the access or the rights to it).
   * A far-reaching or in-depth automation has been created that allows the environment to be re-set up or parts of it to
     be re-set up with a reasonable amount of personnel.