Update generated code for v531

OPENAPI_VERSION

@@ -1 +1 @@
-v530
+v531

lib/stripe/resources/balance_transaction.rb

@@ -3,7 +3,7 @@
 
 module Stripe
   # Balance transactions represent funds moving through your Stripe account.
-  # They're created for every type of transaction that comes into or flows out of your Stripe account balance.
+  # Stripe creates them for every type of transaction that enters or leaves your Stripe account balance.
   #
   # Related guide: [Balance transaction types](https://stripe.com/docs/reports/balance-transaction-types)
   class BalanceTransaction < APIResource

lib/stripe/resources/customer.rb

@@ -2,7 +2,7 @@
 # frozen_string_literal: true
 
 module Stripe
-  # This object represents a customer of your business. It lets you create recurring charges and track payments that belong to the same customer.
+  # This object represents a customer of your business. Use it to create recurring charges and track payments that belong to the same customer.
   #
   # Related guide: [Save a card during payment](https://stripe.com/docs/payments/save-during-payment)
   class Customer < APIResource

lib/stripe/resources/dispute.rb

@@ -3,10 +3,8 @@
 
 module Stripe
   # A dispute occurs when a customer questions your charge with their card issuer.
-  # When this happens, you're given the opportunity to respond to the dispute with
-  # evidence that shows that the charge is legitimate. You can find more
-  # information about the dispute process in our [Disputes and
-  # Fraud](https://stripe.com/docs/disputes) documentation.
+  # When this happens, you have the opportunity to respond to the dispute with
+  # evidence that shows that the charge is legitimate.
   #
   # Related guide: [Disputes and fraud](https://stripe.com/docs/disputes)
   class Dispute < APIResource

lib/stripe/resources/event.rb

@@ -5,32 +5,33 @@ module Stripe
   # Events are our way of letting you know when something interesting happens in
   # your account. When an interesting event occurs, we create a new `Event`
   # object. For example, when a charge succeeds, we create a `charge.succeeded`
-  # event; and when an invoice payment attempt fails, we create an
-  # `invoice.payment_failed` event. Note that many API requests may cause multiple
-  # events to be created. For example, if you create a new subscription for a
-  # customer, you will receive both a `customer.subscription.created` event and a
+  # event, and when an invoice payment attempt fails, we create an
+  # `invoice.payment_failed` event. Certain API requests might create multiple
+  # events. For example, if you create a new subscription for a
+  # customer, you receive both a `customer.subscription.created` event and a
   # `charge.succeeded` event.
   #
-  # Events occur when the state of another API resource changes. The state of that
-  # resource at the time of the change is embedded in the event's data field. For
-  # example, a `charge.succeeded` event will contain a charge, and an
-  # `invoice.payment_failed` event will contain an invoice.
+  # Events occur when the state of another API resource changes. The event's data
+  # field embeds the resource's state at the time of the change. For
+  # example, a `charge.succeeded` event contains a charge, and an
+  # `invoice.payment_failed` event contains an invoice.
   #
   # As with other API resources, you can use endpoints to retrieve an
   # [individual event](https://stripe.com/docs/api#retrieve_event) or a [list of events](https://stripe.com/docs/api#list_events)
   # from the API. We also have a separate
   # [webhooks](http://en.wikipedia.org/wiki/Webhook) system for sending the
-  # `Event` objects directly to an endpoint on your server. Webhooks are managed
-  # in your
-  # [account settings](https://dashboard.stripe.com/account/webhooks),
-  # and our [Using Webhooks](https://stripe.com/docs/webhooks) guide will help you get set up.
+  # `Event` objects directly to an endpoint on your server. You can manage
+  # webhooks in your
+  # [account settings](https://dashboard.stripe.com/account/webhooks). Learn how
+  # to [listen for events]
+  # (/docs/webhooks) so that your integration can automatically trigger reactions.
   #
-  # When using [Connect](https://stripe.com/docs/connect), you can also receive notifications of
-  # events that occur in connected accounts. For these events, there will be an
+  # When using [Connect](https://stripe.com/docs/connect), you can also receive event notifications
+  # that occur in connected accounts. For these events, there's an
   # additional `account` attribute in the received `Event` object.
   #
-  # **NOTE:** Right now, access to events through the [Retrieve Event API](https://stripe.com/docs/api#retrieve_event) is
-  # guaranteed only for 30 days.
+  # We only guarantee access to events through the [Retrieve Event API](https://stripe.com/docs/api#retrieve_event)
+  # for 30 days.
   class Event < APIResource
     extend Stripe::APIOperations::List