Docs - Fix wrong method name in buttons guide

Author: davidjerleke

website/src/content/v9/code-snippets/guides/previous-and-next-buttons/buttons-state-vanilla-01.js

@@ -7,15 +7,15 @@ const nextButtonNode = wrapperNode.querySelector('.embla__next')
 
 const emblaApi = EmblaCarousel(viewportNode, { loop: false })
 
-prevButtonNode.addEventListener('click', () => emblaApi.scrollToPrev(), false)
-nextButtonNode.addEventListener('click', () => emblaApi.scrollToNext(), false)
+prevButtonNode.addEventListener('click', () => emblaApi.goToPrev(), false)
+nextButtonNode.addEventListener('click', () => emblaApi.goToNext(), false)
 
 const toggleButtonsDisabled = (emblaApi) => {
   const setButtonState = (button, enabled) => {
     button.toggleAttribute('disabled', !enabled)
   }
-  setButtonState(prevButtonNode, emblaApi.canScrollToPrev())
-  setButtonState(nextButtonNode, emblaApi.canScrollToNext())
+  setButtonState(prevButtonNode, emblaApi.canGoToPrev())
+  setButtonState(nextButtonNode, emblaApi.canGoToNext())
 }
 
 toggleButtonsDisabled(emblaApi)

website/src/content/v9/pages/guides/alignments.mdx

@@ -38,7 +38,7 @@ Before continuing with this guide, make sure you've completed the following:
 
 ## Understanding alignment
 
-Embla measures each slide's **actual layout position and size** — the values the browser computes after rendering. It then applies the selected [`align`](/api/options/#align) option (`start`, `center`, or `end`) to calculate where each **snap point** should land within the carousel.
+Embla measures each slide's **actual layout position and size** — the values the browser computes after rendering. It then applies the selected [`align`](/docs/api/options/#align) option (`start`, `center`, or `end`) to calculate where each **snap point** should land within the carousel.
 
 The `align` option only affects carousels where slides are **less than 100% of the viewport width**, since full-width slides already occupy the entire scroll area.
 

website/src/content/v9/pages/guides/previous-and-next-buttons.mdx

@@ -84,7 +84,7 @@ If your carousel is [`draggable`](/docs/api/options/#draggable), the **root node
 
 ## Adding buttons
 
-Adding navigation buttons is simple. Create your button elements and connect them to Embla's navigation methods — [`goToPrev`](/docs/api/methods/#goToPrev) and [`goToNext`](/docs/api/methods/#goToNext).
+Adding navigation buttons is simple. Create your button elements and connect them to Embla's navigation methods — [`goToPrev`](/docs/api/methods/#gotoprev) and [`goToNext`](/docs/api/methods/#gotonext).
 
 These methods let you scroll the carousel programmatically when users click the buttons, giving them an intuitive way to move between slides.
 
@@ -191,6 +191,6 @@ We'll handle this by toggling each button's state between **enabled** and **disa
 
 - **Button placement:** Place the prev/next buttons **outside** the Embla root element (the one passed to the initializer, e.g. `.embla__viewport`) to prevent accidental drag interactions.
 - **Looping carousels:** In **looping** carousels with enough slides to wrap around, the prev/next methods always trigger scrolling — buttons are never disabled.
-- **No-op behavior:** On **non-looping** carousels, calling [`goToPrev`](/docs/api/methods/#goToPrev) or [`goToNext`](/docs/api/methods/#goToNext) when already at the first or last slide has no effect. This is normal and ensures consistent, predictable behavior.
+- **No-op behavior:** On **non-looping** carousels, calling [`goToPrev`](/docs/api/methods/#gotoprev) or [`goToNext`](/docs/api/methods/#gotonext) when already at the first or last slide has no effect. This is normal and ensures consistent, predictable behavior.
 
 ---