diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md
index 333d0a1..3e86ae7 100644
--- a/Frequently-Asked-Questions.md
+++ b/Frequently-Asked-Questions.md
@@ -15,7 +15,7 @@
* [I want to render all 100 pages in a document at a high resolution. Is it a good idea?](#allthepages)
* [There are two back-ends, canvas and SVG. Which one should I use?](#backends)
* [PDF.js is fetching the entire PDF file from a server. Can it fetch only the required portions for rendering?](#range)
-* [What is a latest stable version of PDF.js?](#version)
+* [What is the latest stable version of PDF.js?](#version)
* [What types of PDF files are slow in PDF.js? Can I optimize a PDF file to make PDF.js faster?](#optimize)
@@ -201,15 +201,15 @@ You should use the default, which is the canvas back-end, since it is stable and
Actually, PDF.js is doing just that. PDF is a complicated format; in most of the cases, the vital data of a PDF document is located at the end. Depending on [browser support](#faq-support) and on what web server returns the [HTTP Range Requests headers](https://tools.ietf.org/html/rfc7233), PDF.js may automatically start using HTTP Range Requests to fetch not-yet-loaded portions of a PDF needed for rendering visible pages, so a document can be rendered without fully loading it.
-## What is a latest stable version of PDF.js?
+## What is the latest stable version of PDF.js?
PDF.js is a general-purpose library to parse and render PDFs. It is included in a number of projects such as Firefox, a Chromium extension, et cetera. We are recording changes to the library with GitHub [pull requests](https://github.com/mozilla/pdf.js/pulls). The changelog is also available from the Git log.
-The version number consists of three digits: the major release number, minor release number and build number. Before version 1.2, the major and minor numbers were selected when some major milestone was reached. Currently, we are using semantic versioning, where a major version release means that we can introduce API-breaking changes and a minor version release indicates added functionality and backwards compatible changes. The build number is incremented by one each time a new commit is pushed to the master branch. As a sanity check, we accompany each version number with the SHA hash of the latest commit.
+The version number consists of three digits: the major release number, minor release number and build number. Before version 1.2, the major and minor numbers were selected when some major milestone was reached. Currently, we are using semantic versioning, where a major version release means that we can introduce API-breaking changes and a minor version release indicates added functionality and backwards compatible changes. The build number is incremented by one each time a new commit is pushed to the master branch.
We are moving fast and trying to land as much good stuff as we can review and test. The [generic viewer](http://mzl.la/pdf-js) always contains the latest PDF.js build and is available for testing.
-During cooldown period, about once or twice in 6 weeks, we push our library to the [Firefox Nightly](http://nightly.mozilla.org/) channel. We decided to tag/mark our master branch each time we do that, and at this point a beta release is created. To promote a latest beta to a stable release, we listen for feedback (via [GitHub](https://github.com/mozilla/pdf.js/issues), [Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF+Viewer) or [IRC](irc://irc.mozilla.org/%23pdfjs)) from the users and projects that use the PDF.js library. If no critical issues (e.g. a build is unusable, majority of the documents cannot be rendered, etc.) appeared, we promote the build as stable. Otherwise we either discard the release by replacing it by new beta or redo the build with commits that fix a critical issue.
+We regularly (usually weekly or bi-weekly) push the library to the [Firefox Nightly](http://nightly.mozilla.org/) channel. To promote the latest beta to a stable release, we listen for feedback (via [GitHub](https://github.com/mozilla/pdf.js/issues), [Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=PDF+Viewer) or [IRC](irc://irc.mozilla.org/%23pdfjs)) from the users and projects that use the library. If no critical issues (e.g. a build is unusable, major regressions, et cetera) appeared, we promote the build to stable. Otherwise we fix the issues and create a new beta release.
## What types of PDF files are slow in PDF.js? Can I optimize a PDF file to make PDF.js faster?