From 9d814be77f8aac7eb0dd2ee0ed87b450f546c9ae Mon Sep 17 00:00:00 2001 From: Sean Killeen Date: Wed, 19 Oct 2022 22:36:54 -0400 Subject: [PATCH] add automagically --- cSpell.json | 1 + docs/en/API/Auto-API-Controllers.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/cSpell.json b/cSpell.json index b3f09f1b9d..5974d20ae7 100644 --- a/cSpell.json +++ b/cSpell.json @@ -10,6 +10,7 @@ "aspnet", "aspnetcore", "Autofac", + "automagically", "Blazor", "Blazorise", "Boutwell", diff --git a/docs/en/API/Auto-API-Controllers.md b/docs/en/API/Auto-API-Controllers.md index e139c16d20..90ba88f85f 100644 --- a/docs/en/API/Auto-API-Controllers.md +++ b/docs/en/API/Auto-API-Controllers.md @@ -2,7 +2,7 @@ Once you create an [application service](../Application-Services.md), you generally want to create an API controller to expose this service as an HTTP (REST) API endpoint. A typical API controller does nothing but redirects method calls to the application service and configures the REST API using attributes like [HttpGet], [HttpPost], [Route]... etc. -ABP can **automagically** configure your application services as API Controllers by convention. Most of time you don't care about its detailed configuration, but it's possible to fully customize it. +ABP can **"automagically"** configure your application services as API Controllers by convention. Most of time you don't care about its detailed configuration, but it's possible to fully customize it. ## Configuration