update branding (#159)

* update branding

Author: karissarjacobsen

LICENSE

@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2018 DocuSign, Inc. (https://www.docusign.com)
+Copyright (c) 2024 Docusign, Inc. (https://www.docusign.com)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

PAYMENTS_INSTALLATION.md

@@ -1,6 +1,6 @@
 # Configure a payment gateway
 
-DocuSign offers built-in connections to multiple payment gateways. The payments code example uses a developer account via the Stripe gateway service.
+Docusign offers built-in connections to multiple payment gateways. The payments code example uses a developer account via the Stripe gateway service.
 
 
 ## Create a Stripe payment gateway
@@ -9,13 +9,13 @@ DocuSign offers built-in connections to multiple payment gateways. The payments
 
 1. For development, you can skip the Stripe account application by using the **Skip this account form** link at the top of the page.<br />
 
-   ![Skipping the Stripe account form](docs/stripe_skip_account_form_link.png) 
+   ![Skipping the Stripe account form](docs/stripe_skip_account_form_link.png)
 
-   An enabled Stripe payment gateway is now associated with your DocuSign developer account and is shown under **Payment Gateway**.
+   An enabled Stripe payment gateway is now associated with your Docusign developer account and is shown under **Payment Gateway**.
 
 1. Save the **Gateway Account ID** GUID to the code example launcher configuration file.
 
 
 ## Additional documentation
 * [Managing Payment Gateways](https://support.docusign.com/en/guides/managing-payment-gateways)
-* [How to send a request for payment](https://developers.docusign.com/docs/esign-rest-api/how-to/request-a-payment)  
+* [How to send a request for payment](https://developers.docusign.com/docs/esign-rest-api/how-to/request-a-payment)

README.md

@@ -2,64 +2,64 @@
 
 ### GitHub repo: [code-examples-ruby](./README.md)
 
-This GitHub repo includes code examples for the DocuSign Admin API, Click API, eSignature REST API, Monitor API, and Rooms API. To switch between API code examples, modify the `examples_API` setting in the appsettings.yml file. Set only one API type to `true` and set the remaining to `false`.
+This GitHub repo includes code examples for the Docusign Admin API, Click API, eSignature REST API, Monitor API, and Rooms API. To switch between API code examples, modify the `examples_API` setting in the appsettings.yml file. Set only one API type to `true` and set the remaining to `false`.
 
-If none of the API types are set to `true`, the DocuSign eSignature REST API code examples will be shown. If multiple API types are set to `true`, only the first will be shown.
+If none of the API types are set to `true`, the Docusign eSignature REST API code examples will be shown. If multiple API types are set to `true`, only the first will be shown.
 
 ## Introduction
 This repo is a Ruby on Rails application that supports the following authentication workflows:
 
-* Authentication with DocuSign via [Authorization Code Grant](https://developers.docusign.com/platform/auth/authcode).
+* Authentication with Docusign via [Authorization Code Grant](https://developers.docusign.com/platform/auth/authcode).
 When the token expires, the user is asked to re-authenticate. The refresh token is not used.
 
-* Authentication with DocuSign via [JSON Web Token (JWT) Grant](https://developers.docusign.com/platform/auth/jwt/).
+* Authentication with Docusign via [JSON Web Token (JWT) Grant](https://developers.docusign.com/platform/auth/jwt/).
 When the token expires, it updates automatically.
 
 ## eSignature API
 
 For more information about the scopes used for obtaining authorization to use the eSignature API, see [Required scopes](https://developers.docusign.com/docs/esign-rest-api/esign101/auth#required-scopes).
 
-For a list of code examples that use the eSignature API, see the [How-to guides overview](https://developers.docusign.com/docs/esign-rest-api/how-to/) on the DocuSign Developer Center.
+For a list of code examples that use the eSignature API, see the [How-to guides overview](https://developers.docusign.com/docs/esign-rest-api/how-to/) on the Docusign Developer Center.
 
 
 ## Rooms API
 
-**Note:** To use the Rooms API, you must also [create your Rooms developer account](https://developers.docusign.com/docs/rooms-api/rooms101/create-account). Examples 4 and 6 require that you have the DocuSign Forms feature enabled in your Rooms for Real Estate account.
+**Note:** To use the Rooms API, you must also [create your Rooms developer account](https://developers.docusign.com/docs/rooms-api/rooms101/create-account). Examples 4 and 6 require that you have the Docusign Forms feature enabled in your Rooms for Real Estate account.
 For more information about the scopes used for obtaining authorization to use the Rooms API, see [Required scopes](https://developers.docusign.com/docs/rooms-api/rooms101/auth/).
 
-For a list of code examples that use the Rooms API, see the [How-to guides overview](https://developers.docusign.com/docs/rooms-api/how-to/) on the DocuSign Developer Center.
+For a list of code examples that use the Rooms API, see the [How-to guides overview](https://developers.docusign.com/docs/rooms-api/how-to/) on the Docusign Developer Center.
 
 
 ## Click API
 For more information about the scopes used for obtaining authorization to use the Click API, see [Required scopes](https://developers.docusign.com/docs/click-api/click101/auth/#required-scopes)
 
-For a list of code examples that use the Click API, see the [How-to guides overview](https://developers.docusign.com/docs/click-api/how-to/) on the DocuSign Developer Center.
+For a list of code examples that use the Click API, see the [How-to guides overview](https://developers.docusign.com/docs/click-api/how-to/) on the Docusign Developer Center.
 
 
 ## Monitor API
 
-**Note:** To use the Monitor API, you must also [enable DocuSign Monitor for your organization](https://developers.docusign.com/docs/monitor-api/how-to/enable-monitor/).
+**Note:** To use the Monitor API, you must also [enable Docusign Monitor for your organization](https://developers.docusign.com/docs/monitor-api/how-to/enable-monitor/).
 
 For information about the scopes used for obtaining authorization to use the Monitor API, see the [scopes section](https://developers.docusign.com/docs/monitor-api/monitor101/auth/).
 
-For a list of code examples that use the Monitor API, see the [How-to guides overview](https://developers.docusign.com/docs/monitor-api/how-to/) on the DocuSign Developer Center.
+For a list of code examples that use the Monitor API, see the [How-to guides overview](https://developers.docusign.com/docs/monitor-api/how-to/) on the Docusign Developer Center.
 
 
 ## Admin API
 
-**Note:** To use the Admin API, you must [create an organization](https://support.docusign.com/en/guides/org-admin-guide-create-org) in your DocuSign developer account. Also, to run the DocuSign CLM code example, [CLM must be enabled for your organization](https://support.docusign.com/en/articles/DocuSign-and-SpringCM).
+**Note:** To use the Admin API, you must [create an organization](https://support.docusign.com/en/guides/org-admin-guide-create-org) in your Docusign developer account. Also, to run the Docusign CLM code example, [CLM must be enabled for your organization](https://support.docusign.com/en/articles/DocuSign-and-SpringCM).
 
 For information about the scopes used for obtaining authorization to use the Admin API, see the [scopes section](https://developers.docusign.com/docs/admin-api/admin101/auth/).
 
-For a list of code examples that use the Admin API, see the [How-to guides overview](https://developers.docusign.com/docs/admin-api/how-to/) on the DocuSign Developer Center.
+For a list of code examples that use the Admin API, see the [How-to guides overview](https://developers.docusign.com/docs/admin-api/how-to/) on the Docusign Developer Center.
 
 ## Installation
 
 ### Prerequisites
-**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the DocuSign Developer Center, skip items 1 and 2 as they were automatically performed for you.
+**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the Docusign Developer Center, skip items 1 and 2 as they were automatically performed for you.
 
-1. A free [DocuSign developer account](https://go.docusign.com/o/sandbox/); create one if you don't already have one.
-1. A DocuSign app and integration key that is configured for authentication to use either [Authorization Code Grant](https://developers.docusign.com/platform/auth/authcode/) or [JWT Grant](https://developers.docusign.com/platform/auth/jwt/).
+1. A free [Docusign developer account](https://go.docusign.com/o/sandbox/); create one if you don't already have one.
+1. A Docusign app and integration key that is configured for authentication to use either [Authorization Code Grant](https://developers.docusign.com/platform/auth/authcode/) or [JWT Grant](https://developers.docusign.com/platform/auth/jwt/).
 
    This [video](https://www.youtube.com/watch?v=eiRI4fe5HgM) demonstrates how to obtain an integration key.
 
@@ -89,7 +89,7 @@ For a list of code examples that use the Admin API, see the [How-to guides overv
 
 
 ### Installation steps
-**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the DocuSign Developer Center, skip step 4 as it was automatically performed for you.
+**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the Docusign Developer Center, skip step 4 as it was automatically performed for you.
 
 1. Extract the Quickstart ZIP file, or download or clone the code-examples-ruby repository.
 1. In your command-line environment, switch to the folder:
@@ -106,7 +106,7 @@ For a list of code examples that use the Admin API, see the [How-to guides overv
 
 
 ### Installation steps for JWT Grant authentication
-**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the DocuSign Developer Center, skip step 4 as it was automatically performed for you.
+**Note:** If you downloaded this code using [Quickstart](https://developers.docusign.com/docs/esign-rest-api/quickstart/) from the Docusign Developer Center, skip step 4 as it was automatically performed for you.
 Also, in order to select JSON Web Token authentication in the launcher, in config/appsettings.yml, change `quickstart` to `false`.
 
 1. Extract the Quickstart ZIP file or download or clone the code-examples-ruby repository.
@@ -123,11 +123,11 @@ Also, in order to select JSON Web Token authentication in the launcher, in confi
 1. Run the launcher: `rails s`
 1. Open a browser to http://localhost:3000
 1. If it is your first time using the app, grant consent by selecting **Accept**. On the black navigation bar, select **Logout**, then **Login**.
-1. From the picklist, select **JSON Web Token (JWT) grant** > **Authenticate with DocuSign**.
+1. From the picklist, select **JSON Web Token (JWT) grant** > **Authenticate with Docusign**.
 1. Select your desired code example.
 
 ## JWT grant remote signing and Authorization Code Grant embedded signing projects
-See [DocuSign Quickstart overview](https://developers.docusign.com/docs/esign-rest-api/quickstart/overview/) on the DocuSign Developer Center for more information on how to run the JWT grant remote signing project and the Authorization Code Grant embedded signing project.
+See [Docusign Quickstart overview](https://developers.docusign.com/docs/esign-rest-api/quickstart/overview/) on the Docusign Developer Center for more information on how to run the JWT grant remote signing project and the Authorization Code Grant embedded signing project.
 
 
 ### Troubleshooting Windows SSL issue
@@ -147,7 +147,7 @@ Find the root folder for your Ruby gems (in this case, a 64-bit version of Ruby
 
 C:\Ruby27-x64\lib\ruby\gems\2.7.0\gems\
 
-Find the relevant DocuSign Ruby SDK you are using. The name always starts with “docusign”; for instance, DocuSign Click SDK version 1.0.0:
+Find the relevant Docusign Ruby SDK you are using. The name always starts with “docusign”; for instance, Docusign Click SDK version 1.0.0:
 
 C:\Ruby27-x64\lib\ruby\gems\2.7.0\gems\docusign_click-1.0.0\lib\docusign_click
 

app/assets/images/favicon.ico

@@ -58,7 +58,7 @@ def render_examples
   def ds_return
     # To break out of the Quickstart loop an example has been completed
     session[:been_here] = true
-    @title = 'Return from DocuSign'
+    @title = 'Return from Docusign'
     @event = request.params['event']
     @state = request.params['state']
     @envelope_id = request.params['envelopeId']
@@ -69,7 +69,7 @@ def ds_must_authenticate
 
     jwt_auth if session[:api] == 'Monitor'
     redirect_to '/auth/docusign' if Rails.configuration.quickstart && session[:been_here].nil?
-    @title = 'Authenticate with DocuSign'
+    @title = 'Authenticate with Docusign'
     @show_doc = Rails.application.config.documentation
 
     case params[:auth]

app/assets/images/favicon.png

@@ -12,7 +12,7 @@ def create
     # reset the session
     internal_destroy
 
-    Rails.logger.debug "\n==> DocuSign callback Authentication response:\n#{auth_hash.to_yaml}\n"
+    Rails.logger.debug "\n==> Docusign callback Authentication response:\n#{auth_hash.to_yaml}\n"
     Rails.logger.info "==> Login: New token for admin user which will expire at: #{Time.at(auth_hash.credentials['expires_at'])}"
     store_auth_hash_from_docusign_callback
     redirect_to redirect_url

app/controllers/ds_common_controller.rb

@@ -51,21 +51,21 @@ def make_envelope(envelope_args)
 
     # Create the document models
     document1 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc1_b64,
       name: 'Order acknowledgement', # Can be different from actual file name
       fileExtension: 'html', # Many different document types are accepted
       documentId: '1' # A label used to reference the doc
     )
     document2 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc2_b64,
       name: 'Battle Plan', # Can be different from actual file name
       fileExtension: 'docx', # Many different document types are accepted
       documentId: '2' # A label used to reference the do
     )
     document3 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc3_b64,
       name: 'Lorem Ipsum', # Can be different from actual file name
       fileExtension: 'pdf', # Many different document types are accepted
@@ -95,7 +95,7 @@ def make_envelope(envelope_args)
     # Create signHere fields (also known as tabs) on the documents
     # We're using anchor (autoPlace) positioning
     #
-    # The DocuSign platform searches throughout your envelope's documents for matching
+    # The Docusign platform searches throughout your envelope's documents for matching
     # anchor strings. So the sign_here_2 tab will be used in both document 2 and 3
     # since they use the same anchor string for their "signer 1" tabs.
     sign_here1 = DocuSign_eSign::SignHere.new(

app/controllers/session_controller.rb

@@ -57,7 +57,7 @@ def make_template_req
 
     # Create the document model
     document = DocuSign_eSign::Document.new({
-                                              # Create the DocuSign document object
+                                              # Create the Docusign document object
                                               'documentBase64' => base64_file_content,
                                               'name' => 'Lorem Ipsum', # Can be different from actual file name
                                               'fileExtension' => 'pdf', # Many different document types are accepted

app/services/e_sign/eg002_signing_via_email_service.rb

@@ -161,7 +161,7 @@ def make_envelope_json(envelope_args)
     # Create signHere fields (also known as tabs) on the documents,
     # We're using anchor (autoPlace) positioning
     #
-    # The DocuSign platform searches throughout your envelope's documents for matching
+    # The Docusign platform searches throughout your envelope's documents for matching
     # anchor strings. So the sign_here_2 tab will be used in both document 2 and 3
     # since they use the same anchor string for their "signer 1" tabs.
     sign_here1 = DocuSign_eSign::SignHere.new({

app/services/e_sign/eg008_create_template_service.rb

@@ -68,21 +68,21 @@ def make_envelope(envelope_args)
 
     # Create the document models
     document1 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc1_b64,
       name: 'Order acknowledgement', # Can be different from actual file name
       fileExtension: 'html', # Many different document types are accepted
       documentId: '1' # A label used to reference the doc
     )
     document2 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc2_b64,
       name: 'Battle Plan', # Can be different from actual file name
       fileExtension: 'docx', # Many different document types are accepted
       documentId: '2' # A label used to reference the do
     )
     document3 = DocuSign_eSign::Document.new(
-      # Create the DocuSign document object
+      # Create the Docusign document object
       documentBase64: doc3_b64,
       name: 'Lorem Ipsum', # Can be different from actual file name
       fileExtension: 'pdf', # Many different document types are accepted
@@ -112,7 +112,7 @@ def make_envelope(envelope_args)
     # Create signHere fields (also known as tabs) on the documents
     # We're using anchor (autoPlace) positioning
     #
-    # The DocuSign platform searches throughout your envelope's documents for matching
+    # The Docusign platform searches throughout your envelope's documents for matching
     # anchor strings. So the sign_here_2 tab will be used in both document 2 and 3
     # since they use the same anchor string for their "signer 1" tabs.
     sign_here1 = DocuSign_eSign::SignHere.new(

app/services/e_sign/eg010_send_binary_docs_service.rb

@@ -42,7 +42,7 @@ def make_envelope(args)
     #    # NOTA BENE: This method programmatically constructs the
     #    #            order form. For many use cases, it would be
     #    #            better to create the order form as a template
-    #    #            using the DocuSign web tool as WYSIWYG
+    #    #            using the Docusign web tool as WYSIWYG
     #    #            form designer.
     #    #
     #    #################################################################