This is an automated email from the ASF dual-hosted git repository.

earthchen pushed a commit to branch 3.2
in repository https://gitbox.apache.org/repos/asf/dubbo.git


The following commit(s) were added to refs/heads/3.2 by this push:
     new dd70c5a142 Update README.md of  spell errors (#12922)
dd70c5a142 is described below

commit dd70c5a142f029d297c3ed0148cdd51a205f747a
Author: yanfangli <[email protected]>
AuthorDate: Thu Aug 17 14:21:36 2023 +0800

    Update README.md of  spell errors (#12922)
    
    Update README.md of  spell errors
---
 dubbo-spring-boot/dubbo-spring-boot-autoconfigure/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/dubbo-spring-boot/dubbo-spring-boot-autoconfigure/README.md 
b/dubbo-spring-boot/dubbo-spring-boot-autoconfigure/README.md
index 93119160e2..c43f119627 100644
--- a/dubbo-spring-boot/dubbo-spring-boot-autoconfigure/README.md
+++ b/dubbo-spring-boot/dubbo-spring-boot-autoconfigure/README.md
@@ -48,7 +48,7 @@ If your project failed to resolve the dependency, try to add 
the following repos
 
 ## Auto Configuration
 
-Since  `2.5.7`  , Dubbo totally supports Annotation-Driven , core Dubbo's 
components that are registered and initialized in  Spring application context , 
including exterialized configuration features. However , those features need to 
trigger in manual configuration , e.g `@DubboComponentScan` , 
`@EnableDubboConfig` or `@EnableDubbo`.
+Since  `2.5.7`  , Dubbo totally supports Annotation-Driven , core Dubbo's 
components that are registered and initialized in  Spring application context , 
including externalized configuration features. However , those features need to 
trigger in manual configuration , e.g `@DubboComponentScan` , 
`@EnableDubboConfig` or `@EnableDubbo`.
 
 > If you'd like to learn more , please read [Dubbo Annotation-Driven 
 > (Chinese)](http://dubbo.apache.org/zh-cn/blog/dubbo-annotation-driven.html)
 
@@ -181,7 +181,7 @@ The whole Properties Mapping of "Multiple Dubbo Config Bean 
Bindings" lists belo
 
 There is a  different way to identify Multiple Dubbo Config Bean , the 
configuration pattern is like this :
 
-`${config-property-prefix}.${config-bean-id}.${property-name} = some value` , 
let's explain those placehoders : 
+`${config-property-prefix}.${config-bean-id}.${property-name} = some value` , 
let's explain those placeholders : 
 
 - `${config-property-prefix}` : The The prefix of property name for Multiple 
Bindings , e.g. `dubbo.protocols`, `dubbo.applications` and so on.
 - `${config-bean-id}` : The bean id of Dubbo's `*Config`
@@ -217,7 +217,7 @@ If you used advanced IDE tools , for instance [Jetbrains 
IDEA Ultimate](https://
 
 
 
-#### Case 2 - Mutiple Bindings
+#### Case 2 - Multiple Bindings
 
 ![](mconfig-popup-window.png)
 

Reply via email to