From b48ec12f28b0c4f613efd400d9ddd6921112e6da Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Hans=20Pi=C3=B1a?= Date: Tue, 15 Oct 2024 14:02:28 -0300 Subject: [PATCH] docs: fix typo in cookies.mdx (#182) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit fix typo in cookies.mdx which said ¨expiremental¨ instead of ¨experimental¨ --- docs/content/docs/concepts/cookies.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/docs/concepts/cookies.mdx b/docs/content/docs/concepts/cookies.mdx index 88eb5fc7f7..cd29a29d3f 100644 --- a/docs/content/docs/concepts/cookies.mdx +++ b/docs/content/docs/concepts/cookies.mdx @@ -9,7 +9,7 @@ Core Better Auth cookies like `session` and `csrf` will follow `betterauth.${coo All cookies are `httpOnly` and `secure` if the server is running in production mode. -### Cross Subdomain Cookies (🧪 Expiremental) +### Cross Subdomain Cookies (🧪 Experimental) Sometimes you may need to share cookies across subdomains. For example, if you have `app.example.com` and `example.com`, and if you authenticate on `example.com`, you may want to access the same session on `app.example.com`. @@ -80,4 +80,4 @@ Untrusted requests without valid tokens will result in a `403` error. You can also disable CSRF token check for all clients by setting `advanced.disableCSRFCheck` option on the server. You should only do this if your framework handles CSRF protection itself. - \ No newline at end of file +