mashlib 1.7.22-b25a0ff9 → 1.7.22-c82895cd

package/README.md

@@ -24,12 +24,12 @@ One major use of mashlib is as a "databrowser" for a personal data store.
 
 Mashlib is used in SolidOS and contributes to:
 
-- SolidOS Databrowser Frontend - a frontend for Solid Servers like on <solidcommunity.net>
-- SolidOS Data-Kitchen - a stand-alone desktop app: <https://github.com/solid/data-kitchen<>.
+- SolidOS Databrowser Frontend - a frontend for Solid Servers like <solidcommunity.net>
+- SolidOS Data-Kitchen - a stand-alone desktop app: <https://github.com/solid/data-kitchen>
 
-And mashlib is also used standalone as the SolidOS Databrowser Webapp and can be tried out at: <https://solid.github.io/mashlib/dist/browse.html>.
+mashlib is also used stand-alone as the SolidOS Databrowser Webapp and can be tried out at <https://solid.github.io/mashlib/dist/browse.html>.
 
-But mashlib is also used as a library by adding `mashlib.js` (of minified version) directly in your applications. For example:
+mashlib is also used as a library by adding `mashlib.js` (or minified version) directly to your applications. For example:
 
 `<script src="https://solidcommunity.net/mashlib.js"></script>`.
 
@@ -45,15 +45,15 @@ Check out [SolidOS Pod](https://solidos.solidcommunity.net/Team/docs/solidos.htm
 
 The `static/browse.html` page is compiled one to one into the `dist` (output) folder of mashlib and makes mashlib available stand-alone as the SolidOS Databrowser Webapp.
 
-You can see and try out a SolidOS Databrowser Webapp deployment under this link: <https://solid.github.io/mashlib/dist/browse.html>
+You can see and try out a SolidOS Databrowser Webapp deployment at <https://solid.github.io/mashlib/dist/browse.html>.
 
-`browse.html`serves as a perfect example for: Solid WebID authentication and how to make use of mashlib function and variables. 
+`browse.html`serves as a perfect example for Solid WebID authentication and for making use of mashlib functions and variables. 
 
 ### SolidOS Databrowser Frontend
 
-The `src/databrowser.html`page is compiled into the SolidOS Databrowser Frontend which is displayed for each WebID on [solidcommunity.net](https://solidcommunity.net/). This is the case because the [solidcommunity.net](https://solidcommunity.net/) Solid Server is configured with SolidOS as its frontend.
+The `src/databrowser.html`page is compiled into the SolidOS Databrowser Frontend which is displayed for each WebID on [solidcommunity.net](https://solidcommunity.net/). This is the case because the [solidcommunity.net](https://solidcommunity.net/) Solid Server is configured with SolidOS as its front-end.
 
-More information about the SolidOS Frontend and how to use it visit the [User Guide](https://github.com/solid/userguide).
+More information about the SolidOS Front-end and how to use it visit the [User Guide](https://github.com/solid/userguide).
 
 ### SolidOS Data-Kitchen
 
@@ -61,11 +61,11 @@ SolidOS Data-Kitchen uses `mashlib.js`as a direct import in its source code. Vis
 
 ## Mashlib global variables and funtions
 
-If one wants to use mashlib as a direct import (as a package dependency or script import) one needs to know how they immediate available global variables and functions.
+If one wants to use mashlib as a direct import (as a package dependency or script import), one needs to know how they make global variables and functions available.
 
-The availability of these global variables depends on how the sub-modules are imported and exported but also on where the variables are instanciated. For a basic theoretical read please read [this resource](https://www.javatpoint.com/javascript-global-variable).
+The availability of these global variables depends on how the sub-modules are imported and exported and on where the variables are instantiated. For a basic theoretical read, please see [this resource](https://www.javatpoint.com/javascript-global-variable).
 
-What does `global` mean in mashlib? We mean the `global object` which depends on different environments. In mashlib, for now, we use the `window`context which means these variables will not work in non-window contexts such as Node.js environments if directly used. (This does not mean you cannot use mashlib in Node.js environments -> just import it through npm). We will switch this at some point to the [`globalThis`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis).
+What does `global` mean in mashlib? We mean the `global object` which depends on different environments. In mashlib, for now, we use the `window` context which means these variables will not work if directly used in non-window contexts such as `Node.js` environments. (This does not mean you cannot use mashlib in `Node.js` environments; just import it through `npm`). At some point, we will switch this to the [`globalThis`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis).
 
 Next we list the most important window context/global variables and which sub-repos are they exported from:
 

package/dist/mashlib.js

@@ -149178,8 +149178,8 @@ __webpack_require__.r(__webpack_exports__);
 "use strict";
 __webpack_require__.r(__webpack_exports__);
 /* harmony default export */ __webpack_exports__["default"] = ({
-  buildTime: '2022-03-03T08:56:39Z',
-  commit: 'b25a0ff9248e2469f3d08cbd159ba607d5cf415c',
+  buildTime: '2022-03-03T09:01:37Z',
+  commit: 'c82895cd5539097aed4a2e468cb5a2c68d6ec0c2',
   npmInfo: {
     mashlib: '1.7.22',
     npm: '6.14.16',