From 100db19561db9151d3281b716bbd799014012525 Mon Sep 17 00:00:00 2001 From: Sam Umbach Date: Wed, 18 Mar 2015 07:43:16 -0400 Subject: [PATCH] fix minor typo --- Frequently-Asked-Questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md index 99eefa7..39b0e5b 100644 --- a/Frequently-Asked-Questions.md +++ b/Frequently-Asked-Questions.md @@ -156,7 +156,7 @@ PDF.js is a general-purpose library to parse and render PDFs. At the moment it's The version number consists of three digits: the major release number, minor release number and build number. The major and minor number are selected when some major milestone is reached. The build number is incremented by one each time when new a commit is pushed to the master branch. For sanity check, we accompany each version number with the SHA number of the latest commit. -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) and development of version of Firefox PDF Viewer [extension](http://mzl.la/pdf-xpi) always contain the latest PDF.js build and available for testing. +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) and development version of Firefox PDF Viewer [extension](http://mzl.la/pdf-xpi) always contain the latest PDF.js build and 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), [mailing list](https://lists.mozilla.org/listinfo/dev-pdf-js‎), or [IRC](irc://irc.mozilla.org/%23pdfjs)) from the users and projects that use 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 will fix a critical issue.