chore: updated readme

Author: sliedig

README.md

@@ -1,51 +1,32 @@
-![AWS Serverless Developer Experience Workshop Reference Architecture](./docs/workshop_logo.png)
+<img src="./docs/workshop_logo.png" alt="AWS Serverless Developer Experience Workshop Reference Architecture" width="80%" />
 
 # AWS Serverless Developer Experience workshop reference architecture (.NET)
 
 This repository contains the reference architecture for the AWS Serverless Developer Experience workshop.
 
-The AWS Serverless Developer Experience workshop provides you with an immersive experience of a serverless developer.
-The goal is to provide you with an hands-on experience building a serverless solution using
-the [AWS Serverless Application Model (AWS SAM)](https://aws.amazon.com/serverless/sam/) and AWS SAM CLI.
+The AWS Serverless Developer Experience workshop provides you with an immersive experience as a serverless developer. The goal of this workshop is to provide you with hands-on experience building a serverless solution using the [**AWS Serverless Application Model (AWS SAM)**](https://aws.amazon.com/serverless/sam/) and **AWS SAM CLI**.
 
-Along the way, we want to demonstrate principles of event-driven distributed architecture, orchestration, and serverless
-observability, and how to apply them in code.
+Along the way, you will learn about principals of distributed event-driven  architectures, messaging patterns, orchestration, and observability and how to apply them in code. You will explore exciting open-source tools, the core features of Powertools for AWS Lambda, and simplified CI/CD deployments supported by AWS SAM Pipelines.
 
-We'll also explore open-source tools, core features of AWS Lambda Powertools, and serverless CI/CD deployments. You can
-choose choose to run this workshop in a runtime of your choice — Python, TypeScript, Java, and .NET — and work with your
-own developer setup or use AWS Cloud9 to build the services.
+At the end of this workshop, you will be familiar with Serverless developer workflows and microservice composition using AWS SAM, Serverless development best practices, and applied event-driven architectures.
 
-This workshop will take approximately 4 hours to complete. We are assuming that you have some practical development
-skills in one of the supported runtimes, and are familiar with some of the services that we will use in this solution
-which include: [Amazon API Gateway](https://aws.amazon.com/apigateway/), [AWS Lambda](https://aws.amazon.com/lambda/)
-, [Amazon EventBridge](https://aws.amazon.com/eventbridge/)
-, [AWS Step Functions](https://aws.amazon.com/step-functions/) and [Amazon DynamoDB](https://aws.amazon.com/dynamodb/).
-
-## About the Architecture
+## Introducing the Unicorn Properties architecture
 
 ![AWS Serverless Developer Experience Workshop Reference Architecture](./docs/architecture.png)
 
 Our use case is based on a real estate company called **Unicorn Properties**.
 
-As a real estate agency, **Unicorn Properties** needs to manage the publishing of new property listings and sale
-contracts linked to individual properties, and provide a way for their customers to view approved property listings.
+As a real estate agency, **Unicorn Properties** needs to manage the publishing of new property listings and sale contracts linked to individual properties, and provide a way for their customers to view approved property listings.
+
+To support their needs, Unicorn Properties have adopted a serverless, event-driven approach to designing their architecture. This architecture is centred around two primary domains: **Contracts** (managed by the Contracts Service) and **Properties** (managed by the Web and Properties Services).
 
-To support their needs, Unicorn Properties have adopted a serverless, event-driven approach to designing their
-architecture. This architecture is centred around two primary domains: boundaries–Contracts (managed by the Contracts
-Service) and Properties (which are managed by the Properties Web and Properties Services).
+The **Unicorn Contracts** service (namespace: `Unicorn.Contracts`) is a simplified service that manages the contractual relationship between a seller of a property and Unicorn Properties. Contracts are drawn up that define the property for sale, the terms and conditions that Unicorn Properties sets, and how much it will cost the seller to engage the services of the agency.
 
-The **Contracts Service** is a simplified service that manages the contractual relationship between a seller of a
-property and Unicorn Properties. Contracts are drawn up that define the property for sale, the terms and conditions that
-Unicorn Properties sets, and how much it will cost the seller to engage the services of the agency.
+The **Unicorn Web** (namespace: `Unicorn.Web`) manages the details of a property listing to be published on the Unicorn Properties website. Every property listing has an address, a sale price, a description of the property, and some photos that members of the public can look at to get them interested in purchasing the property. Only properties that have been approved for publication can be made visible to the public.
 
-The **Properties Web** service manages the details of a property listing to be published on the Unicorn Properties
-website. Every property listing has an address, a sale price, a description of the property, and some photos that
-members of the public can look at to get them interested in purchasing the property. **Only properties that have been
-approved for publication can be made visible to the public**.
+The **Unicorn Properties** service (namespace: `Unicorn.Properties`) approves a property listings. This service implements a workflow that checks for the existence of a contract, makes sure that the content and the images are safe to publish, and finally checks that the contract has been approved. We don’t want to publish a property until we have an approved contract!
 
-The **Properties Service** approves a listing. This service implements a workflow that checks for the existence of a
-contract, makes sure that the content and the images are safe to publish, and finally checks that the contract has been
-approved. We don’t want to publish a property until we have an approved contract!
+Have a go at building this architecture yourself! Head over to the [Serverless Developer Experience Workshop](https://catalog.workshops.aws/serverless-developer-experience) for more details.
 
 ## Credits