ZhijieYang opened a new pull request #16320:
URL: https://github.com/apache/flink/pull/16320


   ## What is the purpose of the change
   
   Fix the bug that the document address does not match the actual web page
   
   the English page is: 
https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/serialization/third_party_serializers/,but
 the Chinese page 
is:https://ci.apache.org/projects/flink/flink-docs-master/zh/docs/dev/datastream/fault-tolerance/serialization/custom_serializers/.if
 chick the language change button, it does not work.
   
   and I found some links in 
docs/content.zh/docs/dev/datastream/fault-tolerance/serialization/types_serialization.md
 is different from English version, so I modify it in same sense .
   
   ## Brief change log
   
   - Fix the bug from 
`docs/content.zh/docs/dev/datastream/fault-tolerance/serialization/third_party_serializers.md`
   - modify the link form 
`docs/content.zh/docs/dev/datastream/fault-tolerance/serialization/types_serialization.md`
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? no
   


-- 
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.

To unsubscribe, e-mail: [email protected]

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


Reply via email to