Translate docs to english.

docs/content/user-guide/en/getting-started/contributing.md

@@ -1,4 +1,4 @@
-# 贡献
+# Contribution
 
 One of the easiest ways to contribute is to participate in discussions and discuss issues. 
 

docs/content/user-guide/en/getting-started/introduction.md

@@ -1,34 +1,34 @@
-# 介绍
+# Introduction
 
-CAP 是一个EventBus，同时也是一个在微服务或者SOA系统中解决分布式事务问题的一个框架。它有助于创建可扩展，可靠并且易于更改的微服务系统。
+CAP is an EventBus and a solution for solving distributed transaction problems in microservices or SOA systems. It helps create a microservices system that is scalable, reliable, and easy to change.
 
-在微软的 [eShopOnContainer](https://github.com/dotnet-architecture/eShopOnContainers) 微服务示例项目中，推荐使用 CAP 作为生产环境可用的 EventBus。
+In Microsoft's [eShopOnContainer] (https://github.com/dotnet-architecture/eShopOnContainers) microservices sample project, it is recommended to use CAP as the EventBus available in the production environment.
 
-!!! question "什么是 EventBus？"
 
-    An Eventbus is a mechanism that allows different components to communicate with each other without knowing about each other. A component can send an Event to the Eventbus without knowing who will pick it up or how many others will pick it up. Components can also listen to Events on an Eventbus, without knowing who sent the Events. That way, components can communicate without depending on each other. Also, it is very easy to substitute a component. As long as the new component understands the Events that are being sent and received, the other components will never know.
+!!! question "What is EventBus？"
 
-相对于其他的 Service Bus 或者 Event Bus， CAP 拥有自己的特色，它不要求使用者发送消息或者处理消息的时候实现或者继承任何接口，拥有非常高的灵活性。我们一直坚信约定大于配置，所以CAP使用起来非常简单，对于新手非常友好，并且拥有轻量级。
+    An Eventbus is a mechanism that allows different components to communicate with each other without knowing about each other. A component can send an Event to the Eventbus without knowing who will pick it up or how many others will pick it up. Components can also listen to Events on an Eventbus, without knowing who sent the Events. That way, components can communicate without depending on each other. Also, it is very easy to substitute a component. As long as the new component understands the Events that are being sent and received, the other components will never know.
 
-CAP 采用模块化设计，具有高度的可扩展性。你有许多选项可以选择，包括消息队列，存储，序列化方式等，系统的许多元素内容可以替换为自定义实现。
+Compared to other Service Bus or Event Bus, CAP has its own characteristics. It does not require users to implement or inherit any interface when sending messages or processing messages. It has very high flexibility. We have always believed that the appointment is greater than the configuration, so the CAP is very simple to use, very friendly to the novice, and lightweight.
 
+The CAP is modular in design and highly scalable. You have many options to choose from, including message queues, storage, serialization, etc. Many elements of the system can be replaced with custom implementations.
 
-## 相关视频
+## Related videos
 
-[Video: bilibili 教程](https://www.bilibili.com/video/av31582401/)
+[Video: bilibili Tutorial](https://www.bilibili.com/video/av31582401/)
 
-[Video: Youtube 教程](https://youtu.be/K1e4e0eddNE)
+[Video: Youtube Tutorial](https://youtu.be/K1e4e0eddNE)
 
-[Video: 腾讯视频教程](https://www.cnblogs.com/savorboard/p/7243609.html)
+[Video: Tencent Tutorial](https://www.cnblogs.com/savorboard/p/7243609.html)
 
-## 相关文章
+## Related articles
 
-[Article: CAP 介绍及使用](http://www.cnblogs.com/savorboard/p/cap.html)
+[Article: Introduction and how to use](http://www.cnblogs.com/savorboard/p/cap.html)
 
-[Article: CAP 2.5 版本中的新特性](https://www.cnblogs.com/savorboard/p/cap-2-5.html)
+[Article: New features in version 2.5](https://www.cnblogs.com/savorboard/p/cap-2-5.html)
 
-[Article: CAP 2.4 版本中的新特性](http://www.cnblogs.com/savorboard/p/cap-2-4.html)
+[Article: New features in version 2.4](http://www.cnblogs.com/savorboard/p/cap-2-4.html)
 
-[Article: CAP 2.3 版本中的新特性用](http://www.cnblogs.com/savorboard/p/cap-2-3.html)
+[Article: New features in version 2.3](http://www.cnblogs.com/savorboard/p/cap-2-3.html)
 
-[Article: .NET Core Community 首个千星项目诞生：CAP](https://www.cnblogs.com/forerunner/p/ncc-cap-with-over-thousand-stars.html)
+[Article: .NET Core Community The first thousand-star project was born: CAP](https://www.cnblogs.com/forerunner/p/ncc-cap-with-over-thousand-stars.html)

docs/content/user-guide/en/getting-started/quick-start.md

@@ -1,23 +1,23 @@
-# 快速开始
+# Quick Start
 
-了解如何使用 CAP 构建微服务事件总线架构，它比直接集成消息队列提供了哪些优势，它提供了哪些开箱即用的功能。
+Learn how to build a microservices event bus architecture using CAP, which offers advantages over direct integration of message queues, and what out-of-the-box features it provides.
 
-## 安装
+## Installation
 
 ```powershell
 PM> Install-Package DotNetCore.CAP
 ```
 
-## 在 Asp.Net Core 中集成
+##  Integrated in Asp.Net Core
 
-以便于快速启动，我们使用基于内存的事件存储和消息队列。
+For quick start, we use memory-based event storage and message transport.
 
 ```powershell
 PM> Install-Package DotNetCore.CAP.InMemoryStorage
 PM> Install-Package Savorboard.CAP.InMemoryMessageQueue
 ```
 
-在 `Startup.cs` 中，添加以下配置：
+In `Startup.cs` ，add the following configuration:
 
 ```c#
 public void ConfigureServices(IServiceCollection services)
@@ -30,7 +30,7 @@ public void ConfigureServices(IServiceCollection services)
 }
 ```
 
-## 发送消息
+## Publish Message
 
 ```c#
 public class PublishController : Controller
@@ -45,7 +45,7 @@ public class PublishController : Controller
 }
 ```
 
-## 处理消息
+## Process Message
 
 ```C#
 public class ConsumerController : Controller
@@ -59,6 +59,6 @@ public class ConsumerController : Controller
 }
 ```
 
-## 摘要
+## Summary
 
-相对于直接集成消息队列，异步消息传递最强大的优势之一是可靠性，系统的一个部分中的故障不会传播，也不会导致整个系统崩溃。 在 CAP 内部会将消息进行存储，以保证消息的可靠性，并配合重试等策略以达到各个服务之间的数据最终一致性。
+One of the most powerful advantages of asynchronous messaging over direct integrated message queues is reliability, where failures in one part of the system do not propagate or cause the entire system to crash. Messages are stored inside the CAP to ensure the reliability of the message, and strategies such as retry are used to achieve the final consistency of data between services.