📝 Update README.md (#304)

updated features to be consistent with Adam's blog

README.md

@@ -34,25 +34,22 @@
 This is a template for creating a new project using [Clean Architecture](https://ssw.com.au/rules/rules-to-better-clean-architecture/), leveraging [SSW Rules](https://ssw.com.au/rules) & SSW's over 30 years of experience developing software in the Microsoft space.
 
 ## ✨ Features
-
+- 🔨 `dotnet new` cli template - to get you started quickly
+- 📦 Slim - no authentication provider, no authorization & no UI framework
+ - You can add these yourself or use one of our reference architectures from [awesome-clean-architecture](https://github.com/SSWConsulting/awesome-clean-architecture)
+ - as per [ssw.com.au/rules/choosing-authentication/](https://ssw.com.au/rules/choosing-authentication/)
 - 🎯 Domain Driven Design Patterns
  - [Super Hero Domain](./docs/domain.md)
  - AggregateRoot
  - Entity
  - ValueObject
  - DomainEvent
-- ⚖️ EditorConfig - comes with the [SSW.EditorConfig](https://github.com/SSWConsulting/SSW.EditorConfig)
- - Maintain consistent coding styles for individual developers or teams of developers working on the same project using different IDEs
- - as per [ssw.com.au/rules/consistent-code-style/](https://ssw.com.au/rules/consistent-code-style/)
-- 📦 Slim - no authentication provider, no authorization & no UI framework
- - You can add these yourself or use one of our reference architectures from [awesome-clean-architecture](https://github.com/SSWConsulting/awesome-clean-architecture)
- - as per [ssw.com.au/rules/choosing-authentication/](https://ssw.com.au/rules/choosing-authentication/)
 - 🌐 Minimal Endpoints - because it's fast & simple. ⚡
  - Extension methods to ensure consistent HTTP Verbs & Status Codes
-- 🔑 Global Exception Handling - it's important to handle exceptions in a consistent way & protect sensitive information
- - Transforms exceptions into a consistent format following the [RFC7231 memo](https://datatracker.ietf.org/doc/html/rfc7231#section-6.1)
 - 📝 OpenAPI/Swagger - easily document your API
  - as per [ssw.com.au/rules/do-you-document-your-webapi/](https://ssw.com.au/rules/do-you-document-your-webapi/)
+- 🔑 Global Exception Handling - it's important to handle exceptions in a consistent way & protect sensitive information
+ - Transforms exceptions into a consistent format following the [RFC7231 memo](https://datatracker.ietf.org/doc/html/rfc7231#section-6.1)
 - 🗄️ Entity Framework Core - for data access
  - Comes with Migrations & Data Seeding
  - as per [ssw.com.au/rules/rules-to-better-entity-framework/](https://ssw.com.au/rules/rules-to-better-entity-framework/)
@@ -66,13 +63,18 @@ This is a template for creating a new project using [Clean Architecture](https:/
 - 🆔 Strongly Typed IDs - to combat primitive obsession
  - e.g. pass `CustomerId` type into methods instead of `int`, or `Guid`
  - Entity Framework can automatically convert the int, Guid, nvarchar(..) to strongly typed ID.
-- 🔨 `dotnet new` cli template - to get you started quickly
 - 📁 Directory.Build.Props
  - Consistent build configuration across all projects in the solution
  - e.g. Treating Warnings as Errors for Release builds
  - Custom per project
  - e.g. for all test projects we can ensure that the exact same versions of common packages are referenced
  - e.g. XUnit and NSubstitute packages for all test projects
+- ⚖️ EditorConfig - comes with the [SSW.EditorConfig](https://github.com/SSWConsulting/SSW.EditorConfig)
+ - Maintain consistent coding styles for individual developers or teams of developers working on the same project using different IDEs
+ - as per [ssw.com.au/rules/consistent-code-style/](https://ssw.com.au/rules/consistent-code-style/)
+
+
+
 - 🧪 Testing
  - as per [ssw.com.au/rules/rules-to-better-testing/](https://www.ssw.com.au/rules/rules-to-better-testing/)
  - Simpler Unit Tests for Application