From f8bf7fa2df34251983871153d3b880d12d7922ee Mon Sep 17 00:00:00 2001 From: blam Date: Fri, 20 Jan 2023 15:20:06 +0100 Subject: [PATCH] chore: make the lord and almighty saviour vale ahppy. Signed-off-by: blam --- docs/backend-system/core-services/01-index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/backend-system/core-services/01-index.md b/docs/backend-system/core-services/01-index.md index d1e89ba69f..fbf228a937 100644 --- a/docs/backend-system/core-services/01-index.md +++ b/docs/backend-system/core-services/01-index.md @@ -105,7 +105,7 @@ createBackendPlugin({ ### Configuring the service -There's additional options that you can pass to configure the root HTTP Router serivce. These options are passed when you call `createBackend`. +There's additional options that you can pass to configure the root HTTP Router service. These options are passed when you call `createBackend`. - `indexPath` - optional path to forward all unmatched requests to. Defaults to `/api/app` which is the `app-backend` plugin responsible for serving the frontend application through the backend. @@ -229,7 +229,7 @@ createBackendPlugin({ ### Root Logger -The root logger is the logger that is used by other root services. It's where the implemenation lies for creating child loggers around the backstage ecosystem including child loggers for plugins with the correct metadata and annotations. +The root logger is the logger that is used by other root services. It's where the implementation lies for creating child loggers around the backstage ecosystem including child loggers for plugins with the correct metadata and annotations. If you want to override the implementation for logging across all of the backend, this is the service that you should override.