docs(core/buttons): Updated buttons example import paths

[GayatriK2002]

💡 What is the current behavior?

• Example import paths are according to old naming convention.

GitHub Issue Number: #
Jira Issue Number: 3885

🆕 What is the new behavior?

• Example import paths are now updated according to new naming convention

👨‍💻 Help & support

[netlify]

👷 Deploy request for industrial-experience pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	46e418a

[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 button component documentation. It updates the example import paths and component references to align with a new naming convention, ensuring that users are presented with the most current and correct way to implement various button styles.

Highlights

• Documentation Update: The pull request updates the import paths and component names for various button examples within the documentation file docs/components/button/code.mdx.
• Naming Convention Alignment: Old button playground component names like ButtonGhostPlayground, ButtonGreyPlayground, and ButtonDangerOutlinePlayground have been replaced with new, more descriptive names such as ButtonTertiaryPlayground, ButtonSubtlePrimaryPlayground, and ButtonDangerSecondaryPlayground.
• Consistent Examples: The changes ensure that the button examples displayed in the documentation now correctly reflect the latest naming conventions, providing accurate and up-to-date usage guidance.

Changelog

• docs/components/button/code.mdx
  • Updated import statements for button playground components to reflect new naming conventions (e.g., ButtonGhostPlayground changed to ButtonTertiaryPlayground).
  • Replaced instances of old button component tags with their new counterparts within the documentation content (e.g., <ButtonGhostPlayground /> replaced with <ButtonTertiaryPlayground />).

Activity

• No human activity has been recorded on this pull request yet.

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

This pull request updates the import paths and component names for button examples to align with a new naming convention. The changes are straightforward. I have provided one suggestion to improve the semantic structure of the document's headings for better clarity.