fix: correct markdown formatting in README

Author: shoryataneja

README.md

@@ -187,46 +187,42 @@ function HiddenMessage({children}) {
     </div>
   )
 }
+
+export default HiddenMessage
+
+
+# MORE EXAMPLES
 ### Testing <details> / <summary>
 
 HTML `<details>` uses `<summary>` as its toggle button.  
-When testing with React Testing Library, the `<summary>` element is exposed as a
-`button` role, so user interactions can be tested normally.
+When testing with React Testing Library, the `<summary>` element is exposed as a `button` role.
 
 ```js
-import { render, screen } from "@testing-library/react"
-import userEvent from "@testing-library/user-event"
+import { render, screen } from "@testing-library/react";
+import userEvent from "@testing-library/user-event";
 
 function DetailsExample() {
   return (
     <details>
       <summary>More info</summary>
       <p>Hidden content</p>
     </details>
-  )
+  );
 }
 
 test("opens details when summary is clicked", async () => {
-  const user = userEvent.setup()
-  render(<DetailsExample />)
+  const user = userEvent.setup();
+  render(<DetailsExample />);
 
-  const summary = screen.getByRole("button", { name: /more info/i })
+  const summary = screen.getByRole("button", { name: /more info/i });
 
-  // initially closed
-  expect(screen.queryByText("Hidden content")).not.toBeInTheDocument()
+  expect(screen.queryByText("Hidden content")).not.toBeInTheDocument();
 
-  await user.click(summary)
+  await user.click(summary);
 
-  // after clicking, content appears
-  expect(screen.getByText("Hidden content")).toBeInTheDocument()
-})
+  expect(screen.getByText("Hidden content")).toBeInTheDocument();
+});
 
-
-export default HiddenMessage
-```
-
-```jsx
-// __tests__/hidden-message.js
 // these imports are something you'd normally configure Jest to import for you
 // automatically. Learn more in the setup docs: https://testing-library.com/docs/react-testing-library/setup#cleanup
 import '@testing-library/jest-dom'