docs: update links in documentation (#238)

Author: Sitlintac

CONTRIBUTING.md

@@ -34,7 +34,7 @@ We're always looking for more opinions on discussions in the issue tracker. It's
   - This repo is [commitizen friendly](https://github.com/commitizen/cz-cli), so you can use the `cz` cli to help create your commits.
 - Lint and test before submitting the pull request by running `$ npm test`
 - Write a convincing description of why we should land your pull request. Answer _why_ it's needed and provide use-cases.
-- Make the pull request from a [topic branch](https://github.com/dchelimsky/rspec/wiki/Topic-Branches) (not main)
+- Make the pull request from a [topic branch](https://alvinalexander.com/git/git-topic-branch-workflow-pattern-pro-git/) (not main)
 - You might be asked to do changes to your pull request. There's never a need to open another pull request – [just update the existing one.](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md)
 
 ## [Finding contributions to work on](labels/help%20wanted)
@@ -46,12 +46,12 @@ Look at the existing issues for areas of contribution. Searching for issues labe
 ## More about SmartThings
 
 If you are not familiar with SmartThings, we have
-[extensive on-line documentation](https://smartthings.developer.samsung.com/develop/index.html).
+[extensive on-line documentation](https://developer.smartthings.com/docs/getting-started/welcome/).
 
 To create and manage your services and devices on SmartThings, create an account in the
-[developer workspace](https://devworkspace.developer.samsung.com/).
+[developer workspace](https://smartthings.developer.samsung.com/workspace/).
 
-The [SmartThings Community](https://community.smartthings.com/c/developers/) is a good place share and
+The [SmartThings Community](https://community.smartthings.com/) is a good place share and
 ask questions.
 
 There is also a [SmartThings reddit community](https://www.reddit.com/r/SmartThings/) where you
@@ -61,4 +61,4 @@ can read and share information.
 
 Licensed under the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0)
 
-Copyright 2019 SmartThings, Inc.
+Copyright 2023 SmartThings, Inc.

README.md

@@ -47,11 +47,11 @@ SmartApps are custom applications that execute outside of the SmartThings Platfo
 
 There are two distinct options for hosting your SmartApp: AWS Lambda and Webhook.
 
-- **Webhook** SmartApps are any publicly-accessible web server that will receive a POST request payload.
-
 - **AWS Lambda** SmartApps are hosted in the Amazon Web Services cloud and are invoked by ARN instead of a public-DNS address.
 
-To learn more about SmartApps, including choosing the best hosting solution for your SmartApp, visit the [SmartApp developer documentation](https://developer-preview.smartthings.com/docs/connected-services/smartapp-basics).
+- **Webhook** SmartApps are any publicly-accessible web server that will receive a POST request payload.
+
+To learn more about SmartApps, including choosing the best hosting solution for your SmartApp, visit the [SmartApp developer documentation](https://developer.smartthings.com/docs/connected-services/smartapp-basics).
 
 ## Installation
 
@@ -77,7 +77,7 @@ import SmartApp from '@smartthings/smartapp'
 
 The example SmartApp below is the equivalent of a simple Rule (if contact sensor opens/closes, turn lights on/off) which is easily achieved via our Rules API. It is given here as a brief showcase of the SDK, and is not meant to be a good candidate for a SmartApp.
 
->Before hosting your own Automation, be sure to check out [Rules](https://developer-preview.smartthings.com/docs/automations/rules). When all services and Device features involved in a Rule are local, Rules execute locally on a Hub, allowing you to benefit from greater speed, stability, and security than cloud-reliant solutions.
+>Before hosting your own Automation, be sure to check out [Rules](https://developer.smartthings.com/docs/automations/rules). When all services and Device features involved in a Rule are local, Rules execute locally on a Hub, allowing you to benefit from greater speed, stability, and security than cloud-reliant solutions.
 
 ### Running as a Web Service
 
@@ -220,12 +220,12 @@ See the full usage guide on the [project's GitHub repository](https://github.com
 ---
 ## More about SmartThings
 
-Check out our complete developer documentation [here](https://developer-preview.smartthings.com/docs/getting-started/welcome/).
+Check out our complete developer documentation [here](https://developer.smartthings.com/docs/getting-started/welcome).
 
 To create and manage your services and devices on SmartThings, create an account in the
-[developer workspace](https://devworkspace.developer.samsung.com/).
+[developer workspace](https://smartthings.developer.samsung.com/workspace/).
 
-The [SmartThings Community](https://community.smartthings.com/c/developers/) is a good place share and
+The [SmartThings Community](https://community.smartthings.com/) is a good place share and
 ask questions.
 
 There is also a [SmartThings reddit community](https://www.reddit.com/r/SmartThings/) where you
@@ -235,4 +235,4 @@ can read and share information.
 
 Licensed under the [Apache License, Version 2.0](LICENSE)
 
-Copyright 2019 SmartThings, Inc.
+Copyright 2023 SmartThings, Inc.

docs/V2_RELEASE_NOTES.md

@@ -11,10 +11,10 @@ Methods that return lists now return arrays rather that an object with the prope
 is done automatically by the API. The 1.X version of the SDK does not support paging at all in these methods, which
 can result in missed items, such as when a location has more than 200 devices.
 
-This change was also made for consitency, since not all endpoints used the `items`
+This change was also made for consistency, since not all endpoints used the `items`
 object, and for convenience. Since the lists are of limited length and unordered,
 paging is of limited practical use. Most applications, such as displaying a sorted display of items require all pages
-to be retrieved. In the future methods with potentially unbounded numbers of items with inherient order, such as event
+to be retrieved. In the future methods with potentially unbounded numbers of items with inherent order, such as event
 history, will include a paging mechanism.
 
 ### REST API calls are now handled by a separate package
@@ -26,13 +26,13 @@ therefore don't need to use this SDK.
 As a result of the switch to use the [@smartthings/core-sdk](https://www.npmjs.com/package/@smartthings/core-sdk)
 for REST API calls, [Axios](https://www.npmjs.com/package/axios) is now used as the HTTP client rather than
 [request-promise-native](https://www.npmjs.com/package/request-promise-native) (which has been deprecated). As a result, the error object has changed. It's now an instance of the
-[AxiosError](https://github.com/axios/axios/blob/main/index.d.ts#L76-L92) class, so instead of accessing the
+[AxiosError](https://github.com/axios/axios/blob/main/index.d.ts#L12-L41) class, so instead of accessing the
 status of an error response with `.catch(error => {error.statusCode})` you'd do so with
 `.catch(error => {error.response.status})`.
 
 ### All methods return a Promise
 All methods now return a Promise. Before there were some methods that returned void. There was also inconsistency
-in the response of methods that returned no data, with some returning an empty obhect `{}`, others returning an
+in the response of methods that returned no data, with some returning an empty object `{}`, others returning an
 empty string `"`, and still others returning a status value `{"status": "success"}`. Now all such methods return
 a status value.
 

docs/classes/_smart_app_d_.smartapp.md

@@ -3,8 +3,7 @@
 # SmartApp
 
 An instance of the SmartApp class is created to handle lifecycle events for WEBHOOK_SMART_APP, LAMBDA_SMART_APP,
-and API_ONLY apps. Options can either be passed in as parameters to the
-to the constructor, for example:
+and API_ONLY apps. Options can either be passed in as parameters to the constructor, for example:
 ```
 import {SmartApp} from '@smartthings/smartapp'
 ...
@@ -594,7 +593,7 @@ ___
 
 Defines a configuration page that is displayed during app installation and update.
 You can create as many pages as needed to satisfy your configuration needs. See the documentation on
-[how to design pages](https://smartthings.developer.samsung.com/docs/how-to/design-pages-smartapp.html)
+[how to design pages](https://developer.smartthings.com/docs/connected-services/configuration#page-phase)
 for your automation.
 
 **Parameters:**
@@ -621,7 +620,7 @@ ___
 
 ▸ **permissions**(`value`: string | string[]): *[SmartApp](_smart_app_d_.smartapp.md)*
 
-Specify the [OAuth2 scopes](https://smartthings.developer.samsung.com/docs/auth-and-permissions.html#OAuth2-scopes)
+Specify the [OAuth2 scopes](https://developer.smartthings.com/docs/connected-services/oauth-integrations)
 explicitly required by this app. For example `['r:devices:*', and 'x:devices:*']
 to be able to read and control all devices in the location. You do not have to
 provide this list for devices selected by the user in configuration settings.

docs/classes/smartapp.md

@@ -571,7 +571,7 @@ Defines a configuration page that is displayed during app installation and updat
 You can create as many pages as needed to satisfy your configuration needs. See the
 the documentation on how to design pages for your automation.
 
-https://smartthings.developer.samsung.com/docs/how-to/design-pages-smartapp.html
+https://developer.smartthings.com/docs/connected-services/configuration#page-phase
 
 **Parameters:**
 

docs/index.md

@@ -1,6 +1,6 @@
 # SmartApp SDK Reference
 
-The [SmartApp](classes/_smart_app_d_.smartapp.md) class handles all SmartApp [lifecycle events](https://developer-preview.smartthings.com/docs/connected-services/lifecycles) and callbacks. It is instantiated and configured with handlers where appropriate and is invoked in response to either web server HTTP requests, or in response to AWS Lambda function calls. 
+The [SmartApp](classes/_smart_app_d_.smartapp.md) class handles all SmartApp [lifecycle events](https://developer.smartthings.com/docs/connected-services/lifecycles) and callbacks. It is instantiated and configured with handlers where appropriate and is invoked in response to either web server HTTP requests, or in response to AWS Lambda function calls. 
 
 ## Instantiation and Initialization
 

docs/modules/_lifecycle_events_d_.md

@@ -51,7 +51,7 @@ The display mode of the operating system of the client.
 
 • **language**: *string*
 
-Language header representing the client's preferred language. The format of the `Accept-Language` header follows what is defined in [RFC 7231, section 5.3.5](https://tools.ietf.org/html/rfc7231#section-5.3.5)
+Language header representing the client's preferred language. The format of the `Accept-Language` header follows what is defined in [RFC 7231, section 5.3.5](https://www.rfc-editor.org/rfc/rfc7231#section-5.3.5)
 
 ###  os
 

lib/lifecycle-events.d.ts

@@ -400,7 +400,7 @@ export namespace AppEvent {
 		 */
 		version: string
 		/**
-		 * Language header representing the clients preferred language. The format of the `Accept-Language` header follows what is defined in [RFC 7231, section 5.3.5](https://tools.ietf.org/html/rfc7231#section-5.3.5)
+		 * Language header representing the client's preferred language. The format of the `Accept-Language` header follows what is defined in [RFC 7231, section 5.3.5](https://www.rfc-editor.org/rfc/rfc7231#section-5.3.5)
 		 */
 		language: string
 		/**

lib/pages/page.js

@@ -27,7 +27,7 @@ module.exports = class Page {
 	/**
 	 * Define sections for user defined settings. Chain as many as needed.
 	 *
-	 * https://smartthings.developer.samsung.com/docs/how-to/design-pages-smartapp.html#Page-Components
+	 * https://developer.smartthings.com/docs/connected-services/configuration/#sections-and-settings
 	 * @param {String} name Name your section for use in i18n localization keys
 	 * @param {SectionCallback} closure { import("./section") } Chainable section instance
 	 * @returns {Page} Page instance

lib/smart-app.d.ts

@@ -417,7 +417,7 @@ export class SmartApp {
 	/**
 	* Defines a configuration page that is displayed during app installation and update.
 	* You can create as many pages as needed to satisfy your configuration needs. See the documentation on
-	* [how to design pages](https://smartthings.developer.samsung.com/docs/how-to/design-pages-smartapp.html)
+	* [how to design pages](https://developer.smartthings.com/docs/connected-services/configuration#page-phase)
 	* for your automation.
 	*/
 	page(id: string,
@@ -427,7 +427,7 @@ export class SmartApp {
 			configData?: InstalledAppConfiguration) => HandlerResponse): SmartApp
 
 	/**
-	* Specify the [OAuth2 scopes](https://smartthings.developer.samsung.com/docs/auth-and-permissions.html#OAuth2-scopes)
+	* Specify the [OAuth2 scopes](https://developer.smartthings.com/docs/connected-services/oauth-integrations)
 	* explicitly required by this app. For example `['r:devices:*', and 'x:devices:*']
 	* to be able to read and control all devices in the location. You do not have to
 	* provide this list for devices selected by the user in configuration settings.