docs: fix code block language in images-and-fonts docs (#73492)

## Summary
Update incorrect code block languages at [Images and
Fonts](https://nextjs.org/docs/canary/app/getting-started/images-and-fonts)
docs.

### Improving Documentation

- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

Co-authored-by: Delba de Oliveira <[email protected]>

docs/01-app/01-getting-started/04-images-and-fonts.mdx

@@ -55,7 +55,7 @@ The `src` property can be a [local](#local-images) or [remote](#remote-images) i
 
 To use a local image, `import` your `.jpg`, `.png`, or `.webp` image files from your [`public` folder](#handling-static-assets).
 
-```tsx filename="app/page.ts" switcher
+```tsx filename="app/page.tsx" switcher
 import Image from 'next/image'
 import profilePic from './me.png'
 
@@ -131,7 +131,7 @@ Since Next.js does not have access to remote files during the build process, you
 
 Then, to safely allow images from remote servers, you need to define a list of supported URL patterns in `next.config.js`. Be as specific as possible to prevent malicious usage. For example, the following configuration will only allow images from a specific AWS S3 bucket:
 
-```ts filename="next.config.js" switcher
+```ts filename="next.config.ts" switcher
 import { NextConfig } from 'next'
 
 const config: NextConfig = {