Fix links

Author: dshevtsov

docs/architecture/configurations.md

@@ -17,7 +17,7 @@ There are a number of simple attributes that can be configured within the `<type
 | `component`         | View model responsible for rendering the preview and master format. The component does not need to specify the `.js` extension. There are two component types to choose from: `content-type` and `content-type-collection`. Use `Magento_PageBuilder/js/content-type` for static content types that do not have children. Use `Magento_PageBuilder/js/content-type-collection` for content types that can contain children, otherwise known as container content types.                                                                                                                                                                            |
 | `preview_component` | JavaScript file (`preview.js` or `preview-collection.js`) that provides rendering logic within the Admin UI. The preview component does not need to specify the `.js` extension. <br/><br/>For _collection_ content types, you need to either reference your own `preview-collection` component or reference Page Builder's `preview-collection` (`preview_component="Magento_PageBuilder/js/content-type/preview-collection"`). If you don't specify the `preview_component`, Page Builder uses the base `Preview` component shown in the code: `Magento_PageBuilder/js/content-type/preview`.                                                    |
 | `master_component`  | JavaScript file (`master.js` or `master-collection.js`) that provides rendering logic generic for all appearances of your content type when rendered on the storefront. The master component does not need to specify the `.js` extension. <br/><br/>For _collection_ content types, you need to either reference your own `master-collection` component or reference Page Builder's `master-collection` (`master_component="Magento_PageBuilder/js/content-type/master-collection"`). If you don't specify the `master_component`, Page Builder uses the base `Master` component shown in the code: `Magento_PageBuilder/js/content-type/master`. |
-| `form`              | UI component form that provides the form controls for editing your content type. All forms can extend the `pagebuilder_base_form`, which contains boilerplate form configuration and the global Advanced Configuration section. If you decide to omit extending the base form you'll need to ensure you manually declare the various requirements from the base form. See [UiComponent Documentation](http://devdocs.magento.com/guides/v2.4/ui_comp_guide/bk-ui_comps.html) for additional information.                                                                                                                                           |
+| `form`              | UI component form that provides the form controls for editing your content type. All forms can extend the `pagebuilder_base_form`, which contains boilerplate form configuration and the global Advanced Configuration section. If you decide to omit extending the base form you'll need to ensure you manually declare the various requirements from the base form. See [UiComponent Documentation](https://developer.adobe.com/commerce/frontend-core/ui-components/) for additional information.                                                                                                                                           |
 | `sortOrder`         | Optional. The listed order within the menu section. For example, `sortOrder=21` puts the content type third in the `Elements` menu section, after the content types with `sortOrder` values of 10 and 20.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 | `translate`         | Identifies the attribute you want Magento to translate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 

docs/architecture/knockout-bindings.md

@@ -21,7 +21,7 @@ Within Page Builder, we use the `sortable` binding to pass preview-component opt
 
 **Configuration:**
 
-See the options listed on jQuery UI's Sortable API page: http://api.jqueryui.com/sortable/
+See the options listed on jQuery UI's Sortable API page: https://api.jqueryui.com/sortable/
 
 **Usage:**
 
@@ -42,7 +42,7 @@ Within Page Builder, we use this binding for the left panel's content types. You
 
 **Configuration:**
 
-See the options listed on jQuery UI's Sortable API page: http://api.jqueryui.com/draggable/
+See the options listed on jQuery UI's Sortable API page: https://api.jqueryui.com/draggable/
 
 **Usage:**
 

docs/styles/introduction.md

@@ -2,7 +2,7 @@
 
 Page Builder applies CSS styles to both native and custom content types by generating attribute-based CSS rulesets that are unique to each content type on a page. Page Builder generates and applies styles to content types in four stages:
 
--  [Add content-type attributes](#add-content-type-attributes). Page Builder adds a `data-pb-style` attribute and a dynamically generated value to the content type so that it can be uniquely targeted by a CSS selector.
+-  [Add content-type attributes](#content-type-attributes). Page Builder adds a `data-pb-style` attribute and a dynamically generated value to the content type so that it can be uniquely targeted by a CSS selector.
 
 -  [Generate dynamic CSS selectors](#dynamic-css-selectors). Page Builder generates a CSS selector for the content type by combining the page's `html-body` ID and the `data-pb-style` attribute with the content type's unique value.
 

docs/viewports/use-breakpoints.md

@@ -92,7 +92,7 @@ events.on('stage:viewportChangeAfter', function (args) {
 });
 ```
 
-In both handlers, the event handler uses the breakpoint/viewport name to access the `slidesToShow` value, then uses that value to re-initialize the `Products` carousel (the [slick slider](http://kenwheeler.github.io/slick/)) to show a suitable number of products for the selected viewport width, when displayed on the stage.
+In both handlers, the event handler uses the breakpoint/viewport name to access the `slidesToShow` value, then uses that value to re-initialize the `Products` carousel (the [slick slider](https://kenwheeler.github.io/slick/)) to show a suitable number of products for the selected viewport width, when displayed on the stage.
 
 Notice how the viewport data in both event handlers is accessed using dot syntax according to the hierarchy defined in the `view.xml` configuration file. For example, the `preview.ts` file, data for the local `this.slidesToShow` property is accessed using the viewport name from `args`, as shown here: