AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation link text and fixed apostrophe formatting in three places
Security assessment
Changes are purely cosmetic: 1) Breadcrumb link text modified for clarity 2) Curly apostrophes replaced with straight apostrophes in three sentences. No security content was added, modified, or referenced. The changes don't address vulnerabilities, security controls, or security incidents.
Diff
diff --git a/prescriptive-guidance/latest/best-practices-migration-cutover/post-cutover-stage.md b/prescriptive-guidance/latest/best-practices-migration-cutover/post-cutover-stage.md index 1e175833a..5d9b21bc8 100644 --- a//prescriptive-guidance/latest/best-practices-migration-cutover/post-cutover-stage.md +++ b//prescriptive-guidance/latest/best-practices-migration-cutover/post-cutover-stage.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Best practices for cutting over network traffic to AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Best practices for cutting over network traffic to AWS during a migration](introduction.html) @@ -19 +19 @@ After you successfully complete your workload migrations, we recommend communica -Additionally, it’s worth considering any learnings that will help improve the process for future application migrations. You can use a migration score card to measure the success of your migration and communicate overall migration progress across applications and business units. This effort can act as a catalyst for teams to look for opportunities to learn from each other, minimize migration risks, and adopt best practices. +Additionally, it's worth considering any learnings that will help improve the process for future application migrations. You can use a migration score card to measure the success of your migration and communicate overall migration progress across applications and business units. This effort can act as a catalyst for teams to look for opportunities to learn from each other, minimize migration risks, and adopt best practices. @@ -23 +23 @@ Additionally, it’s worth considering any learnings that will help improve the -It’s common for migration projects to have a warranty period in which the migration teams provide support in the event that an issue occurs within a predefined window (typically from one day to one week). It’s important to agree on a suitable timeframe based on the application that you’re migrating. For example, a one-week warranty might not be sufficient if your application runs on a quarterly batch schedule. Furthermore, we recommend that your migration team uses the warranty period to validate that business continuity and disaster recovery elements are configured and working as expected. +It's common for migration projects to have a warranty period in which the migration teams provide support in the event that an issue occurs within a predefined window (typically from one day to one week). It's important to agree on a suitable timeframe based on the application that you're migrating. For example, a one-week warranty might not be sufficient if your application runs on a quarterly batch schedule. Furthermore, we recommend that your migration team uses the warranty period to validate that business continuity and disaster recovery elements are configured and working as expected.