Update generated code (#1379)

* Update generated code for v940

* Update generated code for v945

* Update generated code for v947

* Update generated code for v961

---------

Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
Co-authored-by: Ramya Rao <100975018+ramya-stripe@users.noreply.github.com>

OPENAPI_VERSION

@@ -1 +1 @@
-v938
+v961

lib/stripe/resources/billing/meter.rb

@@ -3,7 +3,7 @@
 
 module Stripe
   module Billing
-    # A billing meter is a resource that allows you to track usage of a particular event. For example, you might create a billing meter to track the number of API calls made by a particular user. You can then use the billing meter to charge the user for the number of API calls they make.
+    # A billing meter is a resource that allows you to track usage of a particular event. For example, you might create a billing meter to track the number of API calls made by a particular user. You can then attach the billing meter to a price and attach the price to a subscription to charge the user for the number of API calls they make.
     class Meter < APIResource
       extend Stripe::APIOperations::Create
       extend Stripe::APIOperations::List

lib/stripe/resources/billing/meter_event_adjustment.rb

@@ -3,7 +3,7 @@
 
 module Stripe
   module Billing
-    # A billing meter event adjustment represents the status of a meter event adjustment.
+    # A billing meter event adjustment is a resource that allows you to cancel a meter event. For example, you might create a billing meter event adjustment to cancel a meter event that was created in error or attached to the wrong customer.
     class MeterEventAdjustment < APIResource
       extend Stripe::APIOperations::Create
 

lib/stripe/resources/forwarding/request.rb

@@ -3,9 +3,9 @@
 
 module Stripe
   module Forwarding
-    # Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.
-    # A config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with
-    # your credentials in the config, and injects card details from the payment_method into the request.
+    # Instructs Stripe to make a request on your behalf using the destination URL. The destination URL
+    # is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials
+    # provided during onboarding, and injects card details from the payment_method into the request.
     #
     # Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers,
     # before storing the request and response data in the forwarding Request object, which are subject to a

lib/stripe/resources/reversal.rb

@@ -14,7 +14,7 @@ module Stripe
   # transfer only if the destination account has enough balance to cover the
   # reversal.
   #
-  # Related guide: [Reversing transfers](https://stripe.com/docs/connect/separate-charges-and-transfers#reversing-transfers)
+  # Related guide: [Reverse transfers](https://stripe.com/docs/connect/separate-charges-and-transfers#reverse-transfers)
   class Reversal < APIResource
     include Stripe::APIOperations::Save
 

lib/stripe/resources/setup_intent.rb

@@ -8,21 +8,21 @@ module Stripe
   #
   # 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
+  # The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/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) 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).
+  # [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+  # to streamline later [off-session payments](https://docs.stripe.com/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 to prevent saving invalid or unoptimized payment methods.
   #
   # 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)
+  # Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
   class SetupIntent < APIResource
     extend Stripe::APIOperations::Create
     extend Stripe::APIOperations::List

lib/stripe/resources/usage_record.rb

@@ -6,6 +6,8 @@ module Stripe
   # metered billing of subscription prices.
   #
   # Related guide: [Metered billing](https://stripe.com/docs/billing/subscriptions/metered-billing)
+  #
+  # This is our legacy usage-based billing API. See the [updated usage-based billing docs](https://docs.stripe.com/billing/subscriptions/usage-based).
   class UsageRecord < APIResource
     OBJECT_NAME = "usage_record"
     def self.object_name