Update 1.2Why use .net core.md (#318)

文档格式修正

Book/1.2Why use .net core.md

@@ -40,7 +40,7 @@ Currently server performance is not too much of a problem, but good performance
 | Cross-Platform | Support | Harder to Support | Support | Harder to Support | Support | Support | Support
 | Support | Support | Support | Support | Support | Support | Support | Support | Support
 | Compilation speed | fast | slow | fast | fast | no compilation | no compilation | no compilation | no compilation
-| Good | Fair | Good | Fair | Poor | Poor | Poor|
+| Readability | Good | Fair | Good | Fair | Poor | Poor | Poor|
 | Game Library and Ecology | Good | Good | Average | Average | Poor | Good | Average|
 | Unity | Unity, UE4 | Not available | Not available | Unity, UE4 | UE4 | Not available | Unity, UE4 | Not available | Unity, UE4 | Not available | Unity, UE4 | Not available
 | IDE Support | Good | Good | Average | Poor | Poor | Poor|
@@ -55,4 +55,4 @@ As you can see from the table. 1:
 6. Erlang performance is poor, functional style is not easy to get started, ide support is poor
 7. C# .net core is very good in every convenience, but can't share code with UE4
 
-Currently Unity is the hottest game engine, C# server with Unity is a perfect match, basically can not find defects.
+Currently Unity is the hottest game engine, C# server with Unity is a perfect match, basically can not find defects.