docs(core): updated toggle button example paths

[GayatriK2002]

💡 What is the current behavior?

• Example import paths are according to old naming convention of toggle button and icon toggle button

GitHub Issue Number: #

🆕 What is the new behavior?

• Example import paths are now updated according to new naming convention of toggle button and icon toggle button

👨‍💻 Help & support

[netlify]

👷 Deploy request for industrial-experience pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	730fd19

[gemini-code-assist]

Summary of Changes

Hello @GayatriK2002, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the accuracy and consistency of the documentation for toggle button components. It updates the example import paths and component references within the code.mdx file to align with recent changes in the component naming conventions, ensuring that users are presented with up-to-date and correct usage examples.

Highlights

• Documentation Updates: The import paths for toggle button and icon toggle button examples have been updated to reflect the new naming conventions.
• Component Naming Alignment: Playground components in the documentation now align with the latest naming structure, replacing older terms like "Primary" and "Outline" with "Tertiary" and "Subtle Secondary" variants.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request successfully updates the example import paths and corresponding JSX components in docs/components/toggle-button/code.mdx to align with the new naming conventions for toggle buttons. This change directly addresses the issue described in the pull request body.

[nuke-ellington]

I think we forgot to add the primary examples?