A bit more clean up

Author: IEvangelist

docs/architecture/distributed-cloud-native-apps-containers/cloud-native-identity/azure-security.md

@@ -45,7 +45,7 @@ As applications become more complicated the number of attack vectors increases a
 
 Penetration testing or "pen testing" involves bringing in external actors to attempt to attack the system. These attackers may be an external consulting company or other developers with good security knowledge from another part of the business. They're given carte blanche to attempt to subvert the system. Frequently, they'll find extensive security holes that need to be patched. Sometimes the attack vector will be something totally unexpected such as a phishing attack against the CEO.
 
-Azure itself is constantly undergoing attacks from a team of hackers inside Microsoft - [Inside the world of the elite hacker and those trying to stop him](https://www.microsoft.com/industry/blog/financial-services/2016/05/17/red-vs-blue/). Over the years, they've been the first to find dozens of potentially catastrophic attack vectors, closing them before they can be exploited externally. The more tempting a target, the more likely that eternal actors will attempt to exploit it and there are a few targets in the world more tempting than Azure.
+Azure itself is constantly undergoing attacks from a team of hackers inside Microsoft. Over the years, they've been the first to find dozens of potentially catastrophic attack vectors, closing them before they can be exploited externally. The more tempting a target, the more likely that eternal actors will attempt to exploit it and there are a few targets in the world more tempting than Azure.
 
 ## Monitoring
 
@@ -270,7 +270,7 @@ While Cosmos DB doesn't provide for supplying customer encryption keys, there ha
 
 ## Keeping secure
 
-Azure has all the tools necessary to release a highly secure product. However, a chain is only as strong as its weakest link. If the applications deployed on top of Azure aren't developed with a proper security mindset and good security audits, then they become the weak link in the chain. There are many great static analysis tools, encryption libraries, and security practices that can be used to ensure that the software installed on Azure is as secure as Azure itself. Examples include [static analysis tools](https://www.mend.io/sca/), [encryption libraries](https://www.libressl.org/), and [security practices](https://www.microsoft.com/industry/blog/financial-services/2016/05/17/red-vs-blue/).
+Azure has all the tools necessary to release a highly secure product. However, a chain is only as strong as its weakest link. If the applications deployed on top of Azure aren't developed with a proper security mindset and good security audits, then they become the weak link in the chain. There are many great static analysis tools, encryption libraries, and security practices that can be used to ensure that the software installed on Azure is as secure as Azure itself. Examples include [static analysis tools](https://www.mend.io/sca/), [encryption libraries](https://www.libressl.org/), and [security practices](/azure/security/fundamentals/best-practices-and-patterns).
 
 >[!div class="step-by-step"]
 >[Previous](code-provenance.md)

docs/architecture/distributed-cloud-native-apps-containers/includes/download-alert.md

@@ -1,15 +1,14 @@
 ---
-ms.date: 04/23/2024
 ms.topic: include
 ---
 
 > [!TIP]
 > :::row:::
 > :::column span="3":::
-> This content is an excerpt from the eBook, Architecture for Distributed Cloud-Native Apps with .NET & Containers, available on [.NET Docs](/dotnet/architecture/TODO) or as a free downloadable PDF that can be read offline.
+> This content is an excerpt from the eBook, Architecture for Distributed Cloud-Native Apps with .NET & Containers, available on [.NET Docs](/dotnet/architecture/distributed-cloud-native-apps-containers) or as a free downloadable PDF that can be read offline.
 >
 > > [!div class="nextstepaction"]
-> > [Download PDF TODO](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf)
+> > [Download PDF](https://aka.ms/aspireebook)
 > :::column-end:::
 > :::column:::
 > :::image type="content" source="../media/cover-thumbnail.png" alt-text=".NET Microservices Architecture for Containerized .NET Applications eBook cover thumbnail.":::

docs/architecture/distributed-cloud-native-apps-containers/index.md

@@ -1,12 +1,12 @@
 ---
 title: Architecture for Distributed Cloud-Native Apps with .NET & Containers
 description: Learn how to build distributed cloud-native applications with .NET and containers.
-ms.date: 10/23/2024
+ms.date: 10/24/2024
 ---
 
 # Architecture for Distributed Cloud-Native Apps with .NET & Containers
 
-![cover image Architecture for Distributed Cloud-Native Apps with .NET & Containers](https://placehold.co/613x793/cyan/magenta.png?text=James,%20we%20need%20this!&font=roboto)
+![cover image Architecture for Distributed Cloud-Native Apps with .NET & Containers](./media/cover.png)
 
 DOWNLOAD available at: <https://aka.ms/aspireebook>
 
@@ -36,11 +36,13 @@ All other marks and logos are property of their respective owners.
 
 Authors:
 
-<!-- TODO: James to fill in... -->
+> **[Geoff Allix](https://github.com/GeoffAllix)**, Chief Technologist, Civica
+
+> **[Alistair Matthews](https://github.com/alistairmatthews)**, Principal Technologist, Civica
 
 Participants and Reviewers:
 
-<!-- TODO: James to fill in... -->
+> **[James Montemagno](https://github.com/jamesmontemagno)**, Principal Lead Program Manager, Developer Community, Microsoft
 
 > **[David Pine](https://github.com/IEvangelist)**, Senior Content Developer, .NET Aspire, Microsoft
 
@@ -50,7 +52,7 @@ Editors:
 
 ## Acknowledgments
 
-This book was inspired by the [.NET Microservices: Architecture for Containerized .NET Applications](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf) and [Architecting Cloud Native .NET Applications for Azure](https://dotnet.microsoft.com/download/e-book/cloud-native-azure/pdf) eBooks. Some chapters were adapted from these eBooks to provide a more focused and in-depth look at building enterprise applications using .NET Aspire.
+This book was inspired by the [.NET Microservices: Architecture for Containerized .NET Applications](https://dotnet.microsoft.com/download/e-book/microservices-architecture/pdf) and [Architecting Cloud Native .NET Applications for Azure](https://dotnet.microsoft.com/download/e-book/cloud-native-azure/pdf) eBooks. Some chapters were adapted from these eBooks to provide a more focused and in-depth look at architecting distributed cloud-native applications using .NET Aspire.
 
 ## Introduction
 
@@ -60,13 +62,13 @@ With the advent of .NET Aspire, it's never been a better time to be a .NET devel
 
 This book is for .NET developers that want to learn how to architect and build distributed cloud-native applications using .NET Aspire. The book assumes that you have a basic understanding of .NET and .NET Aspire. If you are new to .NET Aspire, you can learn more about it in the [Building your first app](/dotnet/aspire/get-started/build-your-first-aspire-app) guide in the .NET Aspire documentation.
 
-## How to use the book
+<!-- TODO: James to fill in...
 
-<!-- TODO: James to fill in... -->
+## How to use the book 
 
 ## What this book doesn't cover
 
-<!-- TODO: James to fill in... -->
+-->
 
 ### Additional resources
 

docs/architecture/distributed-cloud-native-apps-containers/media/cover-thumbnail.png

@@ -58,7 +58,7 @@ We next move to distributed data in cloud-native systems and the benefits and ch
 
 - [gRPC Documentation](https://grpc.io/docs/guides/)
 
-- [Comparing gRPC Services with HTTP APIs](/aspnet/core/grpc/comparison?view=aspnetcore-8.0)
+- [Comparing gRPC Services with HTTP APIs](/aspnet/core/grpc/comparison)
 
 - [Building gRPC Services with .NET video](/Shows/The-Cloud-Native-Show/Building-Microservices-with-gRPC-and-NET)