[RIP-9] update Concept.md in RocketMQ docs/en

docs/en/Concept.md

@@ -6,7 +6,7 @@ RocketMQ message model is mainly composed of Producer, Broker and Consumer. The
 The broker is an independent server during actual deployment, and each broker can store messages from multiple topics. Even messages from the same topic can be stored in the different brokers by sharding strategy.     
 The message queue is used to store physical offsets of messages, and the message addresses are stored in seperate queues. The consumer group consists of multiple consumer instances.    
 ##  2 Producer    
-The Producer is responsible for producing messages, typically by business systems. It sends messages generated by the systems to brokers. RocketMQ provides multiple paradigms of sending: synchronous, asynchronous, sequential and one-way. Both synchronous and asynchronous methods require the confirmation information return from the Broker, but one-way don't need.
+The Producer is responsible for producing messages, typically by business systems. It sends messages generated by the systems to brokers. RocketMQ provides multiple paradigms of sending: synchronous, asynchronous, sequential and one-way. Both synchronous and asynchronous methods require the confirmation information return from the Broker, but one-way method does not require it.
 ## 3 Consumer
 The Consumer is responsible for consuming messages, typically the background system is responsible for asynchronous consumption. The consumer pulls messages from brokers and feeds them into application. From the perspective of user, two types of consumers are provided: pull consumer and push consumer.
 ## 4 Topic
@@ -16,7 +16,7 @@ As the role of the transfer station, the Broker Server stores and forwards messa
 ## 6 Name Server
 The Name Server serves as the provider of routing service. The producer or the consumer can find the list of broker IP addresses for each topic through name server. Multiple name servers can be deployed in one cluster, but they are independent of each other and do not exchange information.
 ## 7 Pull Consumer
-A type of Consumer, the application pulls messages from brokers by actively invoking the consumer's pull message method, and the application has the advantages of controlling the timing and frequency of pulling messages. Once the batch of messages is pulled, user application will initiate consuming process.                    
+A type of Consumer, the application pulls messages from brokers by actively invoking the consumer pull message method, and the application has the advantages of controlling the timing and frequency of pulling messages. Once the batch of messages is pulled, user application will initiate consuming process.                    
 ## 8 Push Consumer
 A type of Consumer. Under this high real-time performance mode, it will push the message to the consumer actively when the Broker receives the data.                       
 ## 9 Producer Group