From bf89fc5abfaaeea723245a2247af597bd86c1a7f Mon Sep 17 00:00:00 2001 From: Dan Kadera Date: Fri, 25 Aug 2023 01:06:43 +0200 Subject: [PATCH] upd docs --- docs/user/03-services-and-dependencies.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user/03-services-and-dependencies.md b/docs/user/03-services-and-dependencies.md index 429f51b..9241f36 100644 --- a/docs/user/03-services-and-dependencies.md +++ b/docs/user/03-services-and-dependencies.md @@ -30,7 +30,7 @@ factory. Services registered this way will not have a public service ID. They will have autogenerated string identifiers beginning with a `#` character, but you're -strongly discouraged from using them, because they're a product of the +strongly discouraged from using these, because they're a product of the compilation process and can change at any time, even between compilations in some cases. Instead, you should rely on injection to get instances of these services. You know, the thing you're using this library for. @@ -46,8 +46,8 @@ more service hooks, you can export a _service definition_ from a resource file. > need to register a given service multiple times, you must provide explicit > definitions for each registration. -As briefly mentioned before, a service definition is a special `satisfies` -expression. This is what it looks like: +As briefly mentioned before, an explicit service definition is a special +`satisfies` expression. This is what it looks like: ```typescript import { ServiceDefinition } from 'dicc';