Update references to Travis in docs

README.md

@@ -1,14 +1,14 @@
 <div align="center">
 <h1><img alt="tldr-pages" src="images/banner-light.png" width=600/></h1>
 
-[![Build status][travis-image]][travis-url]
+[![Build status][github-actions-image]][github-actions-url]
 [![Gitter chat][gitter-image]][gitter-url]
 [![Merged PRs][prs-merged-image]][prs-merged-url]
 [![GitHub contributors][contributors-image]][contributors-url]
 [![license][license-image]][license-url]
 
-[travis-url]: https://travis-ci.org/tldr-pages/tldr/builds
-[travis-image]: https://travis-ci.org/tldr-pages/tldr.svg?branch=master
+[github-actions-url]: https://github.com/tldr-pages/tldr/actions
+[github-actions-image]: https://img.shields.io/github/workflow/status/tldr-pages/tldr/CI.svg
 [gitter-url]: https://gitter.im/tldr-pages/tldr
 [gitter-image]: https://img.shields.io/badge/chat-on_gitter-deeppink
 [prs-merged-url]: https://github.com/tldr-pages/tldr/pulls?q=is:pr+is:merged

contributing-guides/maintainers-guide.md

@@ -55,7 +55,7 @@ as a guideline for current and future maintainers.
 ## II. Handling PRs
 
 - PRs should be merged once they
-  (1) **pass the automated tests** (Travis CI, CLA signing, etc.),
+  (1) **pass the automated tests** (GitHub Actions, CLA signing, etc.),
   (2) have the **review comments addressed**, and
   (3) get **approved reviews by two maintainers**
   (the second maintainer can perform the merge immediately after accepting.)