feat: feeds and general improvements (#51)

Co-authored-by: Vojtech Simetka <[email protected]>

Author: AuHau

docs/user-documentation/getting-started.md

@@ -34,7 +34,7 @@ yarn add @ethersphere/bee-js --save
   <TabItem value="script">
 
 ```html
-<script src="https://unpkg.com/@ethersphere/bee-js/dist/index.js"></script>
+<script src="https://unpkg.com/@ethersphere/bee-js/dist/index.browser.min.js"></script>
 ```
 
   </TabItem>
@@ -76,3 +76,16 @@ That’s it! now you can use the `bee` object.
 :::info Run your own Bee node
 You can find out more about running Bee node in the [Bee docs](https://docs.ethswarm.org/docs/installation/quick-start)
 :::
+
+:::tip Using `<script>` import
+
+If you include `bee-js` using the `unpkg.com` script link then all the exported components will be available to you
+under global namespace `BeeJs`:
+
+```html
+<script src="https://unpkg.com/@ethersphere/bee-js/dist/index.browser.min.js"></script>
+<script>
+  const bee = new BeeJs.Bee('...')
+</script>
+```
+:::

docs/user-documentation/soc-and-feeds.md

@@ -36,11 +36,34 @@ const data = soc.payload()
 
 ### Writing SOCs
 
-When writing a SOC, first, we need to make a writer object. Because we need to sign the chunk, we need to pass in a `signer` object. The `signer` object can be either an Ethereum private key (as a hex string or `Uint8Array`) or an instance of the `Signer` interface. The `Signer` interface can be used for integration with 3rd party Ethereum wallet applications because Swarm uses the same format for signing chunks that Ethereum uses for signing transactions.
+When writing a SOC, first, we need to make a writer object. Because we need to sign the chunk, we need to pass in a `signer` object. The `signer` object can be either an Ethereum private key (as a hex string or `Uint8Array`) or an instance of the [`Signer`](../api/types/signer.md) interface. The `Signer` interface can be used for integration with 3rd party Ethereum wallet applications because Swarm uses the same format for signing chunks that Ethereum uses for signing transactions.
+
+:::info Default `signer`
+
+When you are instantiating `Bee` class you can pass it a default signer that will be used if you won't specify it 
+directly for the `makeSOCWriter`. See [`Bee` constructor](../api/classes/bee.md#constructor) for more info.
+
+:::
+
+:::tip Ethereum Wallet signers
+
+If you want to use your browser Ethereum Wallet like Metamask you can use utility called [`makeEthereumWalletSigner`](../api/functions/utils.eth.makeethereumwalletsigner.md)  that we ship with bee-js
+which creates a [`Signer`](../api/types/signer.md) object out of given EIP-1193 compatible provider.
+
+See it used in our example [here](https://github.com/ethersphere/examples-js/tree/master/eth-wallet-signing).
+
+```js
+import { utils } from '@ethersphere/bee-js'
+
+const signer = utils.Eth.makeEthereumWalletSigner(window.ethereum)
+...
+```
+:::
+
 
 ```ts
-type SyncSigner = (digest: Uint8Array) => Signature
-type AsyncSigner = (digest: Uint8Array) => Promise<Signature>
+type SyncSigner = (digest: Data) => Signature | string
+type AsyncSigner = (digest: Data) => Promise<Signature | string>
 
 /**
  * Interface for implementing Ethereum compatible signing.

docs/user-documentation/upload-download.md

@@ -15,9 +15,9 @@ Uploading your data to Swarm is easy with `bee-js`. Based on your needs you can
 
 ### Data
 
-You can upload and retrieve any `string` or `Uint8Array` data with [`uploadData`](./api/classes/bee#uploaddata) and [`downloadData`](./api/classes/bee#downloaddata) functions.
+You can upload and retrieve any `string` or `Uint8Array` data with [`uploadData`](../api/classes/bee.md#uploaddata) and [`downloadData`](../api/classes/bee.md#downloaddata) functions.
 
-When you download data the return type is [`Data`](./api/types/data) interface which extends `Uint8Array` with convenience functions like:
+When you download data the return type is [`Data`](../api/interfaces/data.md) interface which extends `Uint8Array` with convenience functions like:
 
  - `text()` that converts the bytes into UTF-8 encoded string
  - `hex()` that converts the bytes into **non-prefixed** hex string
@@ -103,7 +103,7 @@ console.log(retrievedFile.data.text()) // prints 'Bee is awesome!'
   </TabItem>
 </Tabs>
 
-In browsers, you can upload directly `File` type. The filename is taken from the file object itself, but can be overwritten through the second argument of the `uploadFile` function (see the [API docs](./api/classes/bee#uploadfile))
+In browsers, you can upload directly `File` type. The filename is taken from the file object itself, but can be overwritten through the second argument of the `uploadFile` function (see the [API docs](../api/classes/bee.md#uploadfile))
 
 <Tabs
   groupId="lang_preferrence"