diff --git a/docusaurus/docs/develop/developer_guide/quickstart.md b/docusaurus/docs/develop/developer_guide/quickstart.md index bf50f3715..de78ec45a 100644 --- a/docusaurus/docs/develop/developer_guide/quickstart.md +++ b/docusaurus/docs/develop/developer_guide/quickstart.md @@ -623,10 +623,9 @@ make supplier3_stake Running `make supplier_list` should now show that all three suppliers are staked. -You can reuse the running `PATH Gateway` to send requests. However, since not all -the `Supplier`s have a `RelayMiner` running, you'll see that initially some of requests will fail. -Meanwhile `PATH Gateway` will build a set of responsive `RelayMiner`s excluding the -failing ones. +You can reuse the running `PATH Gateway` to send requests. Its Quality-of-Service module +will try to handle non-performant suppliers, but you should expect some requests to periodically +fail. Give it a shot by running the following multiple times: diff --git a/docusaurus/docs/operate/quickstart/docker_compose_debian_cheatsheet.md b/docusaurus/docs/operate/quickstart/docker_compose_debian_cheatsheet.md index 8adb2a345..f06a227d8 100644 --- a/docusaurus/docs/operate/quickstart/docker_compose_debian_cheatsheet.md +++ b/docusaurus/docs/operate/quickstart/docker_compose_debian_cheatsheet.md @@ -333,5 +333,4 @@ poktrolld query application show-application $APPLICATION_ADDR docker compose up -d pathgw # View docker logs -f --tail 100 pathgw -``` - \ No newline at end of file +``` \ No newline at end of file diff --git a/docusaurus/docs/operate/run_a_node/hardware_requirements.md b/docusaurus/docs/operate/run_a_node/hardware_requirements.md index 638899540..fc9af1981 100644 --- a/docusaurus/docs/operate/run_a_node/hardware_requirements.md +++ b/docusaurus/docs/operate/run_a_node/hardware_requirements.md @@ -63,8 +63,8 @@ information on what a `PATH Gateway` is. | ----------- | ------- | ----------- | | CPU Cores | 1 | 4 | | RAM | 1GB | 16GB | -| SSD Storage | N/A | N/A | - +| SSD Storage | 5GB | 5GB | + ### Additional Considerations