docs: minor fixes

CHANGELOG.md

@@ -22,7 +22,7 @@ All notable changes to this project will be documented in this file. See [standa
 
 ### BREAKING CHANGES
 
-* **define:** Descriptor property with `connect` key will not translate to `property(value)`.
+* **define:** Property as an object with `connect` key will not translate to `property(value)`.
 
 
 

README.md

@@ -4,7 +4,7 @@
 </h1>
 
 [![npm version](https://img.shields.io/npm/v/hybrids.svg?style=flat)](https://www.npmjs.com/package/hybrids)
-[![bundle size](https://img.shields.io/bundlephobia/minzip/hybrids.svg?label=minzip)](https://bundlephobia.com/result?p=hybrids@1.4.2)
+[![bundle size](https://img.shields.io/bundlephobia/minzip/hybrids.svg?label=minzip)](https://bundlephobia.com/result?p=hybrids)
 [![build status](https://img.shields.io/travis/hybridsjs/hybrids.svg?style=flat)](https://travis-ci.org/hybridsjs/hybrids)
 [![coverage status](https://img.shields.io/coveralls/github/hybridsjs/hybrids.svg?style=flat)](https://coveralls.io/github/hybridsjs/hybrids?branch=master)
 [![gitter](https://img.shields.io/gitter/room/nwjs/nw.js.svg?colorB=893F77)](https://gitter.im/hybridsjs/hybrids)

docs/core-concepts/translation.md

@@ -1,6 +1,6 @@
 # Translation
 
-You can always define properties using [property descriptor](descriptors.md) objects. However, the translation concept provides a set of rules for translating the definition that does not match property descriptor structure. The value can be a primitive, a function, or even an object, but without get and set methods.
+You can always define properties using [property descriptor](descriptors.md) objects. However, the translation concept provides a set of rules for translating the definition that does not match property descriptor structure. The value can be a primitive, a function, or even an object, but without get, set and connect methods.
 
 The translation expands shorter syntax or applies built-in factories using passed values. The translation is done in the following order:
 

docs/template-engine/styling.md

@@ -1,6 +1,6 @@
 # Styling
 
-To style your custom element, you can create `<style>` element directly in the template, use a nested template with styles, or pass text content of thy CSS file.
+To style your custom element, you can create `<style>` element directly in the template, use a nested template with styles, or pass text content of CSS file.
 
 ## Style Element
 
@@ -84,10 +84,11 @@ For external CSS content, use `style` helper method from the result of the `html
   * **returns**:
     * update function compatible with content expression 
 
-Style helper works best with bundlers, which support importing text content of the CSS files (for [Webpack](https://github.com/webpack/webpack) use [css-loader](https://github.com/webpack-contrib/css-loader) without [style-loader](https://github.com/webpack-contrib/style-loader)):
+Style helper works the best with bundlers, which support importing text content of the CSS files (for [Webpack](https://github.com/webpack/webpack) use [css-loader](https://github.com/webpack-contrib/css-loader) without [style-loader](https://github.com/webpack-contrib/style-loader)):
 
 ```javascript
-import styles from './MyElement.css'; // `styles` should contain text content of CSS file
+// `styles` should contain text content of CSS file
+import styles from './MyElement.css';
 
 const MyElement = {
   render: () => html`