diff --git a/src/provider-guides/paddle.mdx b/src/provider-guides/paddle.mdx
index 2acf6646..b1cf0ab0 100644
--- a/src/provider-guides/paddle.mdx
+++ b/src/provider-guides/paddle.mdx
@@ -48,7 +48,7 @@ The Paddle connector supports writing to the following objects:
 
 ### Example integration
 
-For an example manifest file of an Paddle integration, visit our [samples repo on Github](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml).
+For an example manifest with Read Actions, Write Actions, and Proxy Actions, visit our [samples repo on GitHub](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml).
 
 
 ## Creating an API key
@@ -60,7 +60,7 @@ For an example manifest file of an Paddle integration, visit our [samples repo o
 This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.)
 
 To start integrating with Paddle:
-- Create a manifest file using the [example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml).
+- Create a manifest file using the [example](https://github.com/amp-labs/samples/blob/main/paddle/amp.yaml). Add or remove objects based on the Paddle data you want to sync or write.
 - Deploy it using the [amp CLI](/cli/overview).
 - If you are using Read Actions, create a [destination](/destinations).
 - Embed the [InstallIntegration](/embeddable-ui-components#install-integration) UI component.