[flink] branch master updated: [FLINK-18423][docs] Fix Prefer tag in document "Detecting Patterns" page of "Streaming Concepts"

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jark pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/master by this push:
     new a5c2f26  [FLINK-18423][docs] Fix Prefer tag in document "Detecting Patterns" page of "Streaming Concepts"
a5c2f26 is described below

commit a5c2f26a7b799473cfa43acb53d94d24cd33464e
Author: Roc Marshal <64...@users.noreply.github.com>
AuthorDate: Sun Jun 28 00:28:15 2020 -0500

    [FLINK-18423][docs] Fix Prefer tag in document "Detecting Patterns" page of "Streaming Concepts"
    
    This closes #12764
---
 docs/dev/table/streaming/match_recognize.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/dev/table/streaming/match_recognize.md b/docs/dev/table/streaming/match_recognize.md
index 7e9f7f4..b602bb2 100644
--- a/docs/dev/table/streaming/match_recognize.md
+++ b/docs/dev/table/streaming/match_recognize.md
@@ -25,7 +25,7 @@ under the License.
 -->
 
 It is a common use case to search for a set of event patterns, especially in case of data streams.
-Flink comes with a [complex event processing (CEP) library]({{ site.baseurl }}/dev/libs/cep.html)
+Flink comes with a [complex event processing (CEP) library]({% link dev/libs/cep.md %})
 which allows for pattern detection in event streams. Furthermore, Flink's SQL API provides a
 relational way of expressing queries with a large set of built-in functions and rule-based
 optimizations that can be used out of the box.
@@ -93,10 +93,10 @@ project.
 {% endhighlight %}
 
 Alternatively, you can also add the dependency to the cluster classpath (see the
-[dependency section]({{ site.baseurl}}/dev/project-configuration.html) for more information).
+[dependency section]({% link dev/project-configuration.md %}) for more information).
 
 If you want to use the `MATCH_RECOGNIZE` clause in the
-[SQL Client]({{ site.baseurl}}/dev/table/sqlClient.html), you don't have to do anything as all the
+[SQL Client]({% link dev/table/sqlClient.md %}), you don't have to do anything as all the
 dependencies are included by default.
 
 ### SQL Semantics
@@ -263,8 +263,8 @@ look at the [event stream navigation](#pattern-navigation) section.
 ### Aggregations
 
 Aggregations can be used in `DEFINE` and `MEASURES` clauses. Both
-[built-in]({{ site.baseurl }}/dev/table/functions/systemFunctions.html) and custom
-[user defined]({{ site.baseurl }}/dev/table/functions/udfs.html) functions are supported.
+[built-in]({% link dev/table/functions/systemFunctions.md %}) and custom
+[user defined]({% link dev/table/functions/udfs.md %}) functions are supported.
 
 Aggregate functions are applied to each subset of rows mapped to a match. In order to understand
 how those subsets are evaluated have a look at the [event stream navigation](#pattern-navigation)