doc: replacing remaining "widget" references by "component" (#910)

demo/src/routes/+page.svelte

@@ -92,8 +92,9 @@
 			Each component is provided in headless mode in Angular, React and Svelte using the same factory. You can use them with any front-end CSS
 			framework.
 		</LandingCard>
-		<LandingCard title="Consistent">Widgets are provided for Angular, React and Svelte with the exact same markup and functionalities.</LandingCard>
-		<LandingCard title="Accessible">Widgets are designed with a strong emphasis on accessibility and tested for it</LandingCard>
+		<LandingCard title="Consistent">Components are provided for Angular, React and Svelte with the exact same markup and functionalities.</LandingCard
+		>
+		<LandingCard title="Accessible">Components are designed with a strong emphasis on accessibility and tested for it</LandingCard>
 		<LandingCard title="Highly configurable">
 			Default values for all components props are configurable at any point of the application subtree.
 		</LandingCard>

demo/src/routes/docs/[framework]/components/pagination/examples/+page.svelte

@@ -11,13 +11,13 @@
 </Section>
 
 <Section label="Customization" level={2}>
-	<p>The pagination widget is fully customizable, from the page numbers to the arrows.</p>
+	<p>The pagination component is fully customizable, from the page numbers to the arrows.</p>
 	<Sample title="Custom Pagination example" sample={sampleCustom} height={256} />
 </Section>
 
 <Section label="Pagination with hrefs" level={2}>
 	<p>
-		The example shows the pagination widget with hrefs provided for each page element.<br />
+		The example shows the pagination component with hrefs provided for each page element.<br />
 		The <i>hrefs</i> customization is based on <b>pageLink</b> input. This receives a custom function which computes the href using the received page
 		number and the location hash. On the <b>pageChange</b> output event, the location hash is updated with the <i>href</i> of the current page element.
 		This strategy permits navigations in current browser tab, and opening a page in new tabs using the customized href.

demo/src/routes/docs/[framework]/components/progressbar/examples/+page.svelte

@@ -16,7 +16,7 @@
 </Section>
 
 <Section label="Fully customized" level={2}>
-	<p>The display can be fully customized while keeping the widget's functionality and accessibility.</p>
+	<p>The display can be fully customized while keeping the component's functionality and accessibility.</p>
 	<Sample title="Customized progressbar" sample={sampleFullCustom} height={335} />
 </Section>
 

demo/src/routes/docs/[framework]/components/rating/examples/+page.svelte

@@ -9,14 +9,14 @@
 
 <Section label="Default rating" level={2}>
 	<p>
-		The simplest example shows how the user may interact with the widget to set a rating.<br />
+		The simplest example shows how the user may interact with the component to set a rating.<br />
 		The value can be unset by clicking on the current rating.
 	</p>
 	<Sample title="Rating example" sample={sampleDefault} height={130} />
 </Section>
 
 <Section label="Readonly" level={2}>
-	<p>The readonly example below showcases how to disable the widget and use custom star display to support decimal ratings.</p>
+	<p>The readonly example below showcases how to disable the component and use custom star display to support decimal ratings.</p>
 	<Sample title="Read only rating" sample={sampleReadonly} height={95} />
 </Section>
 
@@ -26,7 +26,7 @@
 </Section>
 
 <Section label="Form integration" level={2}>
-	<p>The widget can be integrated in a form as a mandatory field.</p>
+	<p>The component can be integrated in a form as a mandatory field.</p>
 	<Sample title="Form" sample={sampleForm} height={183} />
 </Section>