Added images updated dir update links

Author: heatheramz

public/images/gen-ai/build-settings.png

@@ -295,6 +295,9 @@ export const directory = {
                 {
                   path: 'src/pages/[platform]/build-a-backend/restapi/test-api/index.mdx'
                 },
+                {
+                  path: 'src/pages/[platform]/build-a-backend/restapi/gen-ai/index.mdx'
+                },
                 {
                   path: 'src/pages/[platform]/build-a-backend/restapi/existing-resources/index.mdx'
                 },

public/images/gen-ai/claude.png

@@ -377,7 +377,7 @@ export function override(
 
 Run `amplify push` to sync your changes with the cloud. Now restart your local Next.js server and try to call Amazon Bedrock again through your API route.
 
-![Object with text {completion: "I'm Claude, an AI assistant created by Anthropic"}](/images/gen-ai/claude.png)
+![Object with text completion: "I'm Claude, an AI assistant created by Anthropic"](/images/gen-ai/claude.png)
 
 ## Hosting
 

public/images/gen-ai/login-form.png

@@ -33,40 +33,40 @@ export function getStaticProps(context) {
   };
 }
 
-The Amplify Command Line Interface (CLI) is a unified toolchain to create, integrate, and manage the AWS cloud services for your app.
+The Amplify Command Line Interface (CLI) is a unified toolchain to create, integrate, and manage the AWS cloud services for your app. Follow the steps in our guide to **[Install the Amplify CLI](/[platform]/tools/cli/start/set-up-cli/)**
 
 ![Amplify CLI feature carousel](/assets/cli-b-roll.gif)
 
-<InternalLinkButton href="/cli/start/install">
-  <span slot="text">Install Amplify CLI</span>
-</InternalLinkButton>
-
 ## Key capabilities
 
 ### Data modeling with GraphQL
 
 At the core of most applications is one thing - the data. Easily being able to model and access data in your app allows you to focus on delivering core features and business value instead of architecting and re-architecting your back end.
 
-The GraphQL Transform library allows you to deploy AWS AppSync GraphQL APIs with features like NoSQL databases, authentication, OpenSearch engines, lambda function resolvers, relationships, authorization, and more using GraphQL schema directives. [Learn more](/cli/graphql/overview)
+The GraphQL Transform library allows you to deploy AWS AppSync GraphQL APIs with features like NoSQL databases, authentication, OpenSearch engines, lambda function resolvers, relationships, authorization, and more using GraphQL schema directives. [Learn more](/[platform]/build-a-backend/graphqlapi/)
 
 ### Multiple environments
 
-Amplify CLI has support for multiple environments (e.g. dev, qa, and prod). When you initialize a project with the CLI, you create an Amplify backend environment. Every Amplify backend environment is a container for the categories added to your project. You can view all the backend environments as well as the categories added in the Amplify Console. [Learn more](/cli/teams/overview)
+Amplify CLI has support for multiple environments (e.g. dev, qa, and prod). When you initialize a project with the CLI, you create an Amplify backend environment. Every Amplify backend environment is a container for the categories added to your project. You can view all the backend environments as well as the categories added in the Amplify Console. [Learn more](/[platform]/tools/cli/teams/)
 
 ### Extensibility
 
 Ship fullstack web and mobile apps that you’ll never outgrow, powered by AWS Amplify. AWS Amplify’s extensibility features give developers the flexibility to customize their AWS backend and deployment capabilities. Reconfigure Amplify-generated backend resources to optimize for specific use cases, or modify Amplify's deployment operations to comply with your enterprise DevOps guidelines as your needs evolve.
 
-1. [Override generated resources](/cli/auth/override) - Modify fine-grained backend resource settings and override via CDK. Amplify does the heavy lifting for you. For example, use Amplify to add new Cognito resources with default settings to your backend. Override just the settings you want with 'amplify override auth'. Override [project-level (IAM roles)](/cli/project/override), [auth (Cognito)](/cli/auth/override), and [storage (S3 and DynamoDB)](/cli/storage/override) resources.
-2. [Add custom AWS resources](/cli/custom/cdk) - The Amplify CLI provides the ability to add custom AWS resources with [CDK](/cli/custom/cdk) or [CloudFormation](/cli/custom/cloudformation). Running the 'amplify add custom' command in your Amplify project provides CDK or CloudFormation starter files along with mechanisms to reference other Amplify-generated resources.
-3. [Import existing AWS resources](/cli/auth/import) - Integrate your existing resources, such as [Amazon Cognito user pool and federated identities (identity pool)](/cli/auth/import), or [Storage resources like DynamoDB + S3](/cli/storage/import), into an Amplify project. For example, use your existing Cognito resources as an authentication mechanism for your GraphQL API, Storage (S3), and more.
-4. [Command hooks](/cli/project/command-hooks) - Use Command Hooks to execute custom scripts before, during, and after Amplify CLI commands ('amplify push', 'amplify api gql-compile', and more). Trigger validation checks, run credential scans, or clean-up build artifacts during deployment. Extend Amplify’s best-practice defaults to meet your security guidelines and operational requirements.
+1. [Override generated resources](/[platform]/build-a-backend/auth/override-cognito/) - Modify fine-grained backend resource settings and override via CDK. Amplify does the heavy lifting for you. For example, use Amplify to add new Cognito resources with default settings to your backend. Override just the settings you want with 'amplify override auth'. Override [project-level (IAM roles)](/[platform]/tools/cli/project/override-iam/), [auth (Cognito)](/[platform]/build-a-backend/auth/override-cognito/), and [storage (S3 and DynamoDB)](/[platform]/build-a-backend/storage/modify-amplify-generated-resources/) resources.
+
+2. [Add custom AWS resources](/[platform]/tools/cli/custom/cdk/) - The Amplify CLI provides the ability to add custom AWS resources with [CDK](/[platform]/tools/cli/custom/cdk/) or [CloudFormation](/[platform]/tools/cli/custom/cloudformation/). Running the 'amplify add custom' command in your Amplify project provides CDK or CloudFormation starter files along with mechanisms to reference other Amplify-generated resources.
+
+3. [Import existing AWS resources](/[platform]/build-a-backend/auth/import-existing-resources) - Integrate your existing resources, such as [Amazon Cognito user pool and federated identities (identity pool)](/[platform]/build-a-backend/auth/import-existing-resources/), or [Storage resources like DynamoDB + S3](/[platform]/build-a-backend/storage/import/), into an Amplify project. For example, use your existing Cognito resources as an authentication mechanism for your GraphQL API, Storage (S3), and more.
+
+4. [Command hooks](/[platform]/tools/cli/project/command-hooks/) - Use Command Hooks to execute custom scripts before, during, and after Amplify CLI commands ('amplify push', 'amplify api gql-compile', and more). Trigger validation checks, run credential scans, or clean-up build artifacts during deployment. Extend Amplify’s best-practice defaults to meet your security guidelines and operational requirements.
+
 5. Export Amplify project to CDK - Use Amplify with existing DevOps tools or integrate into your existing deployment systems. Amplify’s export feature lets you export your Amplify project to your preferred tooling using CDK. Export Amplify CLI build artifacts, including CloudFormation templates, GraphQL API resolver code, Lambda function assets, and client-side code generation.
 
 
 ### Local mocking
 
-Amplify supports running a local server for mocking and testing your application before pushing to the cloud with certain categories, including API (AWS AppSync), Storage (Amazon DynamoDB and Amazon S3), Functions (AWS Lambda), and Hosting. After running amplify init you can run the following to start a mock server. [Learn more](/cli/usage/mock)
+Amplify supports running a local server for mocking and testing your application before pushing to the cloud with certain categories, including API (AWS AppSync), Storage (Amazon DynamoDB and Amazon S3), Functions (AWS Lambda), and Hosting. After running amplify init you can run the following to start a mock server. [Learn more](/[platform]/tools/cli/usage/mock/)
 
 ```bash
 amplify mock

src/directory/directory.mjs

@@ -3,7 +3,7 @@ import { getChildPageNodes } from '@/utils/getChildPageNodes';
 
 export const meta = {
   title: 'Start',
-  description: 'Start',
+  description: 'Get started with Amplify CLI unified toolchain to create, integrate, and manage services for your app.',
   platforms: [
     'android',
     'angular',

src/pages/[platform]/build-a-backend/restapi/gen-ai/index.mdx

@@ -30,11 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-It is highly recommended that you complete the Getting Started section of Amplify setup before using local mocking.
-
-<InternalLinkButton href="/start">
-  <span slot="text">Get Started</span>
-</InternalLinkButton>
+It is highly recommended that you complete the **[Getting Started](/[platform]/start/getting-started/)** section of Amplify setup before using local mocking.
 
 In order to quickly test and debug without pushing all changes in your project to the cloud, Amplify supports _Local Mocking and Testing_ for certain categories including API (AWS AppSync), Storage (Amazon DynamoDB and Amazon S3), and Functions (AWS Lambda). This includes using directives from the GraphQL Transformer, editing & debug resolvers, hot reloading, JWT mocking of authorization checks, and even performing S3 operations such as uploading and downloading content.