lowercase(server-migration): rename mixed case filenames, #85

Azure · Apr 25, 2022 · 1fe5498 · 1fe5498
1 parent c4a0ef0
commit 1fe5498
Show file tree

Hide file tree

Showing 8 changed files with 4 additions and 4 deletions.
diff --git a/content/migration/server-migration/overview.md b/content/migration/server-migration/overview.md
@@ -23,5 +23,5 @@ During this phase, typically missed but important, each migration wave identifie
 ## [**Waves Migration & Post Go-Live Milestone**](./migration.md) 
 During this phase, each migration wave is cutover to Azure and validated for expected functionality. For Post Go-live, each migration wave is handed over to Azure operations teams for the defined soak period. 
 
-![Concept Diagram](./png/LiftandShift-dcmigration-workflow.PNG)
+![Concept Diagram](./png/liftandshift-dcmigration-workflow.png)
 
diff --git a/...png/LiftandShift-dcmigration-workflow.PNG → ...png/liftandshift-dcmigration-workflow.png b/...png/LiftandShift-dcmigration-workflow.PNG → ...png/liftandshift-dcmigration-workflow.png
diff --git a/...rver-migration/png/migration-workflow.PNG → ...rver-migration/png/migration-workflow.png b/...rver-migration/png/migration-workflow.PNG → ...rver-migration/png/migration-workflow.png
diff --git a/...er-migration/png/replication-workflow.PNG → ...er-migration/png/replication-workflow.png b/...er-migration/png/replication-workflow.PNG → ...er-migration/png/replication-workflow.png
diff --git a/...on/server-migration/png/scan-workflow.PNG → ...on/server-migration/png/scan-workflow.png b/...on/server-migration/png/scan-workflow.PNG → ...on/server-migration/png/scan-workflow.png
diff --git a/content/migration/server-migration/replication.md b/content/migration/server-migration/replication.md
@@ -13,7 +13,7 @@ The following content can be used as a checklist to incorporate within your migr
 ## **2 Replication Tools Planning and Implementation** 
 ### &nbsp;&nbsp;&nbsp;&nbsp;2.1\.  Plan for replication agents/appliances that will be needed to replicate the migration waves. 
 
-![Concept Diagram](./png/replication-workflow.PNG)
+![Concept Diagram](./png/replication-workflow.png)
 
 - &nbsp;&nbsp;&nbsp;&nbsp;Reference Link A: https://docs.microsoft.com/en-us/azure/migrate/migrate-support-matrix-vmware-migration#vm-requirements-agentless
 - &nbsp;&nbsp;&nbsp;&nbsp;Reference Link B: https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-vmware-agent

diff --git a/content/migration/server-migration/scan.md b/content/migration/server-migration/scan.md
@@ -10,7 +10,7 @@ The following content can be used as a checklist to incorporate within your migr
 
 ### &nbsp;&nbsp;&nbsp;&nbsp;1.1\.  Plan for scanning agents/appliances that will be needed to discover the state. 
 
-![Concept Diagram](./png/scan-workflow.PNG)
+![Concept Diagram](./png/scan-workflow.png)
 
 - &nbsp;&nbsp;&nbsp;&nbsp;Reference Link A: https://docs.microsoft.com/en-us/azure/migrate/tutorial-discover-vmware#set-up-the-appliance
 - &nbsp;&nbsp;&nbsp;&nbsp;Reference Link B: https://docs.microsoft.com/en-us/azure/migrate/tutorial-discover-hyper-v#set-up-the-appliance

diff --git a/content/migration/server-migration/testing.md b/content/migration/server-migration/testing.md
@@ -88,7 +88,7 @@ This is usually led by application owners. For example, UAT may include:
 
 The below diagram aims to provide a workflow for testing and migration based on common scenarios. Timelines for different aspects of the workflow, such as testing vs. migration, may be targeted on different dates depending on your scenario.
 
-![Concept Diagram](./png/migration-workflow.PNG)
+![Concept Diagram](./png/migration-workflow.png)
 
 ## **3 Migration Plan Execution**