From 47e9a3fe40d7f2168b032a66862fa1ab69a69420 Mon Sep 17 00:00:00 2001
From: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
Date: Wed, 4 Oct 2023 17:39:53 +0000
Subject: [PATCH] Update generated code for v580

---
 OPENAPI_VERSION                      |  2 +-
 lib/stripe/resources/setup_intent.rb | 23 +++++++++++------------
 2 files changed, 12 insertions(+), 13 deletions(-)

diff --git a/OPENAPI_VERSION b/OPENAPI_VERSION
index 23f3997c9..f8eb31b2e 100644
--- a/OPENAPI_VERSION
+++ b/OPENAPI_VERSION
@@ -1 +1 @@
-v576
\ No newline at end of file
+v580
\ No newline at end of file
diff --git a/lib/stripe/resources/setup_intent.rb b/lib/stripe/resources/setup_intent.rb
index 9de4c88f1..f494b8601 100644
--- a/lib/stripe/resources/setup_intent.rb
+++ b/lib/stripe/resources/setup_intent.rb
@@ -3,25 +3,24 @@
 
 module Stripe
   # A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.
-  # For example, you could use a SetupIntent to set up and save your customer's card without immediately collecting a payment.
+  # For example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.
   # Later, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.
   #
-  # Create a SetupIntent as soon as you're ready to collect your customer's payment credentials.
-  # Do not maintain long-lived, unconfirmed SetupIntents as they may no longer be valid.
-  # The SetupIntent then transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+  # Create a SetupIntent when you're ready to collect your customer's payment credentials.
+  # Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
+  # The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
   # you through the setup process.
   #
   # Successful SetupIntents result in payment credentials that are optimized for future payments.
-  # For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) may need to be run through
-  # [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) at the time of payment method collection
-  # in order to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
-  # If the SetupIntent is used with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer), upon success,
-  # it will automatically attach the resulting payment method to that Customer.
+  # For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
+  # [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
+  # to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+  # If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
+  # it automatically attaches the resulting payment method to that Customer after successful setup.
   # We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
-  # PaymentIntents to save payment methods in order to prevent saving invalid or unoptimized payment methods.
+  # PaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.
   #
-  # By using SetupIntents, you ensure that your customers experience the minimum set of required friction,
-  # even as regulations change over time.
+  # By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
   #
   # Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
   class SetupIntent < APIResource