chore: Update documentation spelling errors

docs/trd/cloud-infrastructure.md

@@ -1,6 +1,6 @@
 # Deployment View
 
-In order to make the application scalable we need to dockerize the layers. Layers that will be registered in azure container registries are the front-end and the back-end layers. The data layer will not be placed inside the Azure Container Apps. Azure Container Apps only supports AzureFiles SMB shares for persistent storage. This is an issue as Postgres requires hardlinks and AzureFiles SMB doesn't support hardlinks. So we won't be able to mount a persistent storage that works for postgres inside Azure Container Apps. We will therefor make use of Azure PostgreSQL
+In order to make the application scalable we need to dockerize the layers. Layers that will be registered in azure container registries are the front-end and the back-end layers. The data layer will not be placed inside the Azure Container Apps. Azure Container Apps only supports AzureFiles SMB shares for persistent storage. This is an issue as Postgres requires hardlinks and AzureFiles SMB doesn't support hardlinks. So we won't be able to mount a persistent storage that works for postgres inside Azure Container Apps. We will therefor make use of Azure Flexible PostgreSQL
 
 ## Docker Containers
 
@@ -28,7 +28,7 @@ Azure Container Registry is a managed registry service based on the open-source
 
 We use container registries with our existing container development and deployment pipelines to build container images in Azure. Building on demand, or fully automate builds with triggers such as source code commits and base image updates.
 
-Azure container registries allows you to deploy, store and build docker containers on Azure. When deploying from Azure container apps these container registires are referenced. Our container registry has two containers regsitered. One for the BE and one fro the FE respectively.
+Azure container registries allows you to deploy, store and build docker containers on Azure. When deploying from Azure container apps these container registries are referenced. Our container registry has two containers registered. One for the BE and one for the FE respectively.
 
 ## Azure Container App Environment
 
@@ -56,7 +56,7 @@ Serverless computing offers services that manage and maintain servers, which rel
 
 ![Azure Container Apps](/azure-container-apps.png)
 
-## Azure PostgreSQL
+## Azure Flexible PostgreSQL
 
 Azure Database for PostgreSQL flexible server is a fully managed database service designed to provide more granular control and flexibility over database management functions and configuration settings. The service generally provides more flexibility and server configuration customizations based on user requirements. The flexible server architecture allows users to collocate the database engine with the client tier for lower latency and choose high availability within a single availability zone and across multiple availability zones. Azure Database for PostgreSQL flexible server instances also provide better cost optimization controls with the ability to stop/start your server and a burstable compute tier ideal for workloads that don't need full compute capacity continuously
 
@@ -65,7 +65,7 @@ Azure Database for PostgreSQL flexible server is a fully managed database servic
 The storage used for the database and backup is encrypted by default with service managed keys. Data encryption additionally encrypts the databases, backups and logs at rest without any changes to the application.
 
 - Automated patching
-- Atomatic backups
+- Automatic backups
 - Adjust performance and scale in seconds
 - Stop/Start server to lower TCO
 - Enterprise grade security
@@ -76,7 +76,7 @@ The storage used for the database and backup is encrypted by default with servic
 
 ## CI/CD
 
-Continuous integration and continuous deployment of containers is set up via the github repository. On the developer's local machine a dockerfile is added to the root folder to instruct the containerization steps when building the container. This is pushed with the code to Github. Also in the root folder is .github/workflows where you can find the Github actions that are configured for specific actions on specific branches. For instance on merge or on push to main branch would trigger the build process and if the build is succesful will then deploy the artifacts to the remote Azure Container Registry. The remote container registry then reversions and rebuilds the container on server and deploys to the Azure Container Apps.
+Continuous integration and continuous deployment of containers is set up via the Github repository. On the developer's local machine a dockerfile is added to the root folder to instruct the containerization steps when building the container. This is pushed with the code to Github. Also in the root folder is .github/workflows where you can find the Github actions that are configured for specific actions on specific branches. For instance on merge or on push to main branch would trigger the build process and if the build is succesful will then deploy the artifacts to the remote Azure Container Registry. The remote container registry then reversions and rebuilds the container on server and deploys to the Azure Container Apps.
 
 ![CI/CD pipeline](/cicd.png)