From 064eb8947268bd3fd58d146a1e73d08c005e8e41 Mon Sep 17 00:00:00 2001 From: Jordi Enric <37541088+jordienr@users.noreply.github.com> Date: Thu, 11 Jul 2024 15:13:12 +0200 Subject: [PATCH] typos --- docs/docs.logflare.com/docs/backends/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs.logflare.com/docs/backends/index.mdx b/docs/docs.logflare.com/docs/backends/index.mdx index 923bbc71c..5c74cf0f2 100644 --- a/docs/docs.logflare.com/docs/backends/index.mdx +++ b/docs/docs.logflare.com/docs/backends/index.mdx @@ -4,7 +4,7 @@ By default, the Logflare service offers managed BigQuery as a backend automatica If your plan is BYOB, your provided BigQuery configurations will disable ingestion into Logflare's managed BigQuery. -Logflare's mutli-backend capabilities allows 3rd party services and other data storage engines to be used together for purposes such as data redundancy, integrations and more. +Logflare's multi-backend capabilities allows 3rd party services and other data storage engines to be used together for purposes such as data redundancy, integrations and more. :::info Multi-backend support is a private alpha feature. Contact us if you wish to preview these features. @@ -12,7 +12,7 @@ Multi-backend support is a private alpha feature. Contact us if you wish to prev When there are multiple attached backends, the Logflare service will always insert into the managed BigQuery (or a configured BYOB), as well as any other attached backends to that source. -As such, a backend can be attched to multiple sources, and the underlying data storage mechanisms will be automatically managed by Logflare. Details for each are further explained in the documentation for each backend. +As such, a backend can be attached to multiple sources, and the underlying data storage mechanisms will be automatically managed by Logflare. Details for each are further explained in the documentation for each backend. A backend can be any one of the following types: