dianfu commented on a change in pull request #13791:
URL: https://github.com/apache/flink/pull/13791#discussion_r513132764



##########
File path: docs/dev/table/tableApi.zh.md
##########
@@ -24,7 +24,7 @@ under the License.
 
 The Table API is a unified, relational API for stream and batch processing. 
Table API queries can be run on batch or streaming input without modifications. 
The Table API is a super set of the SQL language and is specially designed for 
working with Apache Flink. The Table API is a language-integrated API for 
Scala, Java and Python. Instead of specifying queries as String values as 
common with SQL, Table API queries are defined in a language-embedded style in 
Java, Scala or Python with IDE support like autocompletion and syntax 
validation. 
 
-The Table API shares many concepts and parts of its API with Flink's SQL 
integration. Have a look at the [Common Concepts & API]({{ site.baseurl 
}}/dev/table/common.html) to learn how to register tables or to create a 
`Table` object. The [Streaming Concepts](./streaming) pages discuss streaming 
specific concepts such as dynamic tables and time attributes.
+The Table API shares many concepts and parts of its API with Flink's SQL 
integration. Have a look at the [Common Concepts & API]({% link 
dev/table/common.md %}) to learn how to register tables or to create a `Table` 
object. The [Streaming Concepts](./streaming) pages discuss streaming specific 
concepts such as dynamic tables and time attributes.

Review comment:
       ```suggestion
   The Table API shares many concepts and parts of its API with Flink's SQL 
integration. Have a look at the [Common Concepts & API]({% link 
dev/table/common.zh.md %}) to learn how to register tables or to create a 
`Table` object. The [Streaming Concepts](./streaming) pages discuss streaming 
specific concepts such as dynamic tables and time attributes.
   ```
   Same for the other places.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to