updated the section name + copy

Author: mindapivessa

docs/docs.json

@@ -428,9 +428,9 @@
             ]
           },
           {
-            "group": "Design & UX Standards",
+            "group": "Design Guidelines",
             "pages": [
-              "mini-apps/design-ux/design-patterns",
+              "mini-apps/design-ux/best-practices",
               "mini-apps/design-ux/onchainkit"
             ]
           },

docs/images/minikit/Publisher.png

@@ -1,5 +1,5 @@
 ---
-title: Design Patterns
+title: Best Practices
 description: Design best practices for Mini Apps
 ---
 
@@ -12,23 +12,18 @@ description: Design best practices for Mini Apps
 
 ![Metadata Guidelines](/images/minikit/mobile-first.png)
 
-### Onboarding and guest experiences
+### First impression and user onboarding
 - Your app metadata will be the first thing a new user will see, and is what they’ll base their first impression on. Aim for your metadata to provide helpful context, and properly set expectations with new users on what your app does.
-Consider the experience for new users opening your app for the first time. Include your value props, a light onboarding flow, or easy access to guides / FAQs from your homepage to help new users orient themselves
-- No technical jargon - language is user-friendly
-- Value is immediately apparent to new users
-- Defer auth until needed. Triggering the auth tray as the first thing a user sees on app open can create a jarring experience, and asks users to take an action they may not be confident in before demonstrating the value of your app.
-- Include a splash page for sign-in if needed.
-- Consider adding a “guest” mode, allowing users to explore your app before asking them to sign in.
+- Consider the experience for new users opening your app for the first time. Include your value props, a light and delightful onboarding flow, or easy access to guides / FAQs from your homepage to help new users orient themselves.
+- Consider adding a “guest” mode, allowing users to explore your app before asking them to sign in. Defer auth until needed. Triggering the auth tray as the first thing a user sees on app open can create a jarring experience, and asks users to take an action they may not be confident in before demonstrating the value of your app.
 
 ![Metadata Guidelines](/images/minikit/metadata-guidelines.png)
 
-
 ### Gasless transactions
 Enable users to transact on your apps without needing gas by using wallet solutions that support gas sponsorship like [Base Account and Paymaster](/base-account/improve-ux/sponsor-gas/paymasters).
 
 ### Legible identity
-Never use wallet addresses. Instead, leverage identity solutions like ENS and [Basenames](/base-account/basenames/basenames-onchainkit-tutorial).
+Never display wallet addresses as default usernames. Instead, leverage identity solutions like ENS and [Basenames](/base-account/basenames/basenames-onchainkit-tutorial).
 
 ### Localization
 Many of our users are located around the world. Apps that are localised for each region will perform significantly better. For next.js apps, you can use Next.js Internationalization to localize your app.