Skip to content
Browse files

Typos

  • Loading branch information...
1 parent 9b57e63 commit 69932dc006beef795573f50085110d22d2119bd8 khamza committed
Showing with 3 additions and 3 deletions.
  1. +3 −3 README.md
View
6 README.md
@@ -13,7 +13,7 @@ IndexedDB Polyfill
### 1. Introduction
Indexed Database API, or IndexedDB API, on its own is an API for browsers to support client-side storages. This API is implemented on Mozilla Firefox (since version 4), and Google Chrome (since version 11), and should be implemented in Internet Explorer in the next release version 10 [\[1\]][1]. However it is unknown whether it will be implemented by other browsers, as you can see from the link.
-[Polyfilling] [polyfill-wiki] fills that gap by relying on the other capabilities of a browser. So :IndexedDB polyfill" is just a project that is intended to make other browsers "mimic" IndexedDB API. It uses Web SQL Database API, which is another client-side storage API, as a back-end.
+[Polyfilling] [polyfill-wiki] fills that gap by relying on the other capabilities of a browser. So "IndexedDB polyfill" is just a project that is intended to make other browsers "mimic" IndexedDB API. It uses Web SQL Database API, which is another client-side storage API, as a back-end.
The core design of IndexedDB API is databases with key-value tables, which are called ObjectStores. However unlike basic localStorage (sessionStorage), caching and other "key-value" alike storage APIs, it supports Indexing, Cursors, Key Generators, and Transactions. The IndexedDB API documentation[\[2\]][2] describes both synchronous and asynchronous API, but only the second one is implemented in Mozilla and Chrome. In general, the API is pretty flexible.
@@ -23,7 +23,7 @@ Documentation: <http://www.w3.org/TR/IndexedDB>
### 2. Using the library
All you have to do is to include _indexeddb.polyfill.js_ file into your web page:
-> `<`script type="text/javascript" src="indexedDB.polyfill.debug.js">`<`/script>
+> `<`script type="text/javascript" src="indexedDB.polyfill.js">`<`/script>
If the target browser does not support IndexedDB, the polyfill automatically creates _indexedDB_ global object and thus exposes its functionality. So you do not have to modify anything in your existing project with IndexedDB code. If the target browser has native implementation of IndexedDB, the polyfill will not interfere with it.
@@ -34,7 +34,7 @@ To run unit tests open _index.html_ in target browser. To verify unit tests agai
The project also includes tests imported from [W3C-tests.org] [3] (see References section)
### 4. Performance Tests
-All the database related routines, such as adding, deleting, clearing, creating indexes, cursors, can be testing for performance benchmarks using _test/benchmark.html_ tool.
+All the database related routines, such as adding, deleting, clearing, creating indexes, cursors, can be tested for performance benchmarks using _test/benchmark.html_ tool.
### 5. Open issues

0 comments on commit 69932dc

Please sign in to comment.
Something went wrong with that request. Please try again.