s

collections/developers/flist/flist_case_studies/flist_nextcloud_case_study.md

@@ -179,7 +179,7 @@ We can see in the first section (`trusted_proxies static`) that we set a range o
 
 After the global config at the top, the line `{$DOMAIN}:{$PORT}` defines the port that Caddy will listen to and the domain that we are using for our site. This is important, because in the case that port `443` is specified, Caddy will handle SSL certificates automatically.
 
-The following blocks define behavior for different URL paths that users might try to access. 
+The following slice define behavior for different URL paths that users might try to access. 
 
 To begin, we have `/aio*`. This is how we place the AIO management app in a "subfolder" of our main domain. To accomplish that we need a few rules that rewrite the contents of the returned pages to correct the links. We also add some text replacements here to accomplish the enhancements mentioned earlier, like automatically filling the domain entry field.
 

collections/developers/internals/zos/internals/network/deploy_network_v2.md

@@ -36,7 +36,7 @@ But we need to stress the importance of IPv6 availability when you're running a
 grid is boldly claiming to be a new Internet, we should make sure we adhere to the new protocols that are future-proof. 
 Hence: IPv6 is the base, and IPv4 is just there to accomodate the transition.
 
-Nowadays, RIPE can't even hand out consecutive /22 IPv4 blocks any more for new LIRs, so you'll be bound to market to 
+Nowadays, RIPE can't even hand out consecutive /22 IPv4 slice any more for new LIRs, so you'll be bound to market to 
 get IPv4, mostly at rates of 10-15 Euro per IP. Things tend to get costly that way.
 
 So anyway, IPv6 is not an afterthought in 0-OS, we're starting with it.

collections/developers/internals/zos/internals/network/network_v2.md

@@ -36,7 +36,7 @@ But we need to stress the importance of IPv6 availability when you're running a
 grid is boldly claiming to be a new Internet, we should make sure we adhere to the new protocols that are future-proof. 
 Hence: IPv6 is the base, and IPv4 is just there to accomodate the transition.
 
-Nowadays, RIPE can't even hand out consecutive /22 IPv4 blocks any more for new LIRs, so you'll be bound to market to 
+Nowadays, RIPE can't even hand out consecutive /22 IPv4 slice any more for new LIRs, so you'll be bound to market to 
 get IPv4, mostly at rates of 10-15 Euro per IP. Things tend to get costly that way.
 
 So anyway, IPv6 is not an afterthought in 0-OS, we're starting with it.

collections/developers/tfchain/farming_policies.md

@@ -63,7 +63,7 @@ A council member can create a Farming Policy (DAO) in the following way:
 6: Select an actions `tfgridModule` -> `createFarmingPolicy` and fill in all the fields.
 7: Create a forum post with the details of the farming policy and fill in the link of that post in the `link` field
 8: Give it some good `description`.
-9: Duration is optional (by default it's 7 days). A proposal cannot be closed before the duration is "expired". If you wish to set a duration, the duration should be expressed in number of blocks from `now`. For example, 2 hours is equal to 1200 blocks (blocktime is 6 seconds) in this case, the duration should be filled in as `1200`.
+9: Duration is optional (by default it's 7 days). A proposal cannot be closed before the duration is "expired". If you wish to set a duration, the duration should be expressed in number of slice from `now`. For example, 2 hours is equal to 1200 slice (blocktime is 6 seconds) in this case, the duration should be filled in as `1200`.
 10: If all the fields are filled in, click `Propose`, now Farmers can vote. A proposal can be closed manually once there are enough votes AND the proposal is expired. To close go to extrinsics -> `dao` -> `close` -> fill in proposal hash and index (both can be found in chainstate).
 
 All (su, cu, nu, ipv4) values should be expressed in units USD. Minimal uptime should be expressed as integer that represents an percentage (example: `95`).
@@ -86,7 +86,7 @@ First identify the policy ID to link to a farm. You can check for farming polici
 6: Limits contains a `farming_policy_id` (Required) and cu, su, end, node count (which are all optional). It also contains `node_certification`, if this is set to true only certified nodes can have this policy.
 7: Create a forum post with the details of why we want to link that farm to that policy and fill in the link of that post in the `link` field
 8: Give it some good `description`.
-9: Duration is optional (by default it's 7 days). A proposal cannot be closed before the duration is "expired". If you wish to set a duration, the duration should be expressed in number of blocks from `now`. For example, 2 hours is equal to 1200 blocks (blocktime is 6 seconds) in this case, the duration should be filled in as `1200`.
+9: Duration is optional (by default it's 7 days). A proposal cannot be closed before the duration is "expired". If you wish to set a duration, the duration should be expressed in number of slice from `now`. For example, 2 hours is equal to 1200 slice (blocktime is 6 seconds) in this case, the duration should be filled in as `1200`.
 10: If all the fields are filled in, click `Propose`, now Farmers can vote. A proposal can be closed manually once there are enough votes AND the proposal is expired. To close go to extrinsics -> `dao` -> `close` -> fill in proposal hash and index (both can be found in chainstate).
 
 For reference: