docs(doc): update reamde

README.md

@@ -6,17 +6,17 @@
 [![npm version](https://badge.fury.io/js/fronts.svg)](http://badge.fury.io/js/fronts)
 ![license](https://img.shields.io/npm/l/fronts)
 
-`Fronts` is a progressive micro frontends framework for building Web applications, and it's based on the [module federation](https://webpack.js.org/concepts/module-federation/) of Webpack.
+Fronts is a progressive micro frontends framework for building Web applications, and it's based on the [module federation](https://webpack.js.org/concepts/module-federation/) of Webpack.
 
 ## Motivation
 
 Among the many micro frontends solutions, [single-spa](https://github.com/single-spa/single-spa) and [Module Federation](https://webpack.js.org/concepts/module-federation/) are the best of them.
 
 [single-spa](https://github.com/single-spa/single-spa) is a micro frontends framework based on router configuration. The centralization of configuration brings some limitations, such as it is difficult to granulate nestable micro frontends, module granularity control, module sharing, and so on.
 
-In 2019, Zack Jackson proposed and implemented Module Federation. Module Federation is a completely different concept from single-spa, and allows a JavaScript application to dynamically load code from another application. It completely solves the problem of code dependency sharing and runtime modularity. The idea is true - "[A game-changer in JavaScript architecture](https://medium.com/swlh/webpack-5-module-federation-a-game-changer-to-javascript-architecture-bcdd30e02669)" as mentioned in Zack Jackson's article. And it's currently supported by Webpack, Next.js, and Rollup.
+In 2019, Zack Jackson proposed and implemented Module Federation. Module Federation is a completely different concept from single-spa, and allows a JavaScript application to dynamically load code from another application. It completely solves the problem of code dependency sharing and runtime modularity. The idea is true - [A game-changer in JavaScript architecture](https://medium.com/swlh/webpack-5-module-federation-a-game-changer-to-javascript-architecture-bcdd30e02669) as mentioned in Zack Jackson's article. And it's currently supported by Webpack, Next.js, and Rollup.
 
-Although the Module Federation concept is so amazing, it has not yet gone further to provide a more complete and fully targeted micro frontends framework implementation, and this is what `Fronts` is trying to do.
+Although the Module Federation concept is so amazing, it has not yet gone further to provide a more complete and fully targeted micro frontends framework implementation, and this is what Fronts is trying to do.
 
 ## Features
 
@@ -31,10 +31,11 @@ Although the Module Federation concept is so amazing, it has not yet gone furthe
 - **Monorepo & TypeScript** - Friendly support for Monorepo and TypeScript, which are mutually appropriate technology stack.
 - **Version control** - It's used for efficient and dynamic delivery apps such as canary release.
 - **Zero hijacking** - Fronts didn't do any hijacking, maintaining originality and possible loss of performance and security.
+- **Generic Communication** - Fronts provides concise and generic communication APIs, which supports almost all frontend environments.
 
 ## Getting Started
 
-> You can follow this article(["React without create-react-app Webpack 5"](https://dev.to/rogeliosamuel621/react-without-create-react-app-webpack-5-1b1o)) to quickly create `app1` and `app2` React projects.
+> You can follow this article([React without create-react-app Webpack 5](https://dev.to/rogeliosamuel621/react-without-create-react-app-webpack-5-1b1o)) to quickly create `app1` and `app2` React projects.
 
 Assuming you've completed these steps, let's get started with a quick taste of the wonderful micro frontends development of Fronts.