diff --git a/docs/quickstart/publish_cli.md b/docs/quickstart/publish_cli.md
index 73da49936..82296776f 100644
--- a/docs/quickstart/publish_cli.md
+++ b/docs/quickstart/publish_cli.md
@@ -119,6 +119,9 @@ Possible next steps include:
 
 - Check out [the lifecycle of data in IPFS](../concepts/lifecycle.md) to learn more about how publishing by pinning fits into the full lifecycle of data in IPFS.
 - Try fetching the pinned file by following the [retrieval quickstart](./retrieve.md).
+
+In addition to self-hosting, IPFS publishing can be augmented with third-party commercial services:
+
 - If you prefer to upload a file programmatically with JavaScript or Go, check out the [Web3.storage docs](https://web3.storage/docs/how-tos/store/).
 - Alternatively, try out [Filebase](https://filebase.com/), a pinning service that offers an [AWS S3-compatible API for pinning](https://docs.filebase.com/getting-started/s3-api-getting-started-guide), so you can use any S3-compatible SDK, e.g. [aws-sdk](https://www.npmjs.com/package/aws-sdk), and [many](https://github.com/s3tools/s3cmd) more.
 - You can also try out [Functionland Fula network](https://fx.land), a pinning service that provides a true globally distributed and individually-owned nodes [Fula Network](https://docs.fx.land). The SDK supports [mobile-native applications](../../concepts/usage-ideas-examples.md#mobile-native-applications) and offers built-in encryption.