ENGDOCS-1600-scoutAndGetStarted (#18090)

* ENGDOCS-1600-scoutAndGetStarted

* resize image

* fix images

---------

Co-authored-by: Allie Sadler <alliesadler@f693mt7fh6.home>

content/get-started/07_multi_container.md

@@ -17,7 +17,7 @@ container or run it separately?" In general, each container should do one thing
 
 And there are more reasons. So, like the following diagram, it's best to run your app in multiple containers.
 
-![Todo App connected to MySQL container](images/multi-app-architecture.png)
+![Todo App connected to MySQL container](images/multi-container.png?w=350h=250)
 
 
 ## Container networking

content/scout/integrations/registry/ecr.md

@@ -22,32 +22,7 @@ resources, see [CloudFormation stack template](#cloudformation-stack-template).
 
 The following diagram shows how the Docker Scout ECR integration works.
 
-```mermaid
-sequenceDiagram
-	autonumber
-	box User
-		participant User
-	end
-	box User's AWS
-		participant EventBridge
-		participant SNSTopic
-		participant SecretsManager
-	  participant ECR
-	end
-	box Docker Scout
-		participant Scout API
-	end
-
-	# During setup
-  SNSTopic ->> Scout: CloudFormation Stack Event
-  Scout ->> SecretsManager: Set up Scout credentials for EventBridge
-
-	# After integration
-  User ->> ECR: Push an image
-  EventBridge -->> Scout: Push image Event
-  Scout ->> ECR: Login, and pull image
-  ECR ->> Scout: Pull image
-```
+![How the ECR integration works](../../images/Scout-ECR.png)
 
 After the integration, Docker Scout automatically pulls and analyzes images
 that you push to the ECR registry. Metadata about your images are stored on the