docs: small text improvements and updated numbers (#4920)

mrosvik · mimarz · Copilot · web-flow · commit 13cce037293a · 2026-06-02T15:56:19.000+02:00
Co-authored-by: Michael Marszalek &lt;mimarz@gmail.com&gt;
Co-authored-by: Copilot Autofix powered by AI &lt;175728472+Copilot@users.noreply.github.com&gt;
diff --git a/apps/www/app/content/blog/en/designsystemet-web-pre2.mdx b/apps/www/app/content/blog/en/designsystemet-web-pre2.mdx
@@ -1,6 +1,6 @@
 ---
 title: "@digdir/designsystemet-web prerelease 2"
-description: Second prerelease of the @digdir/designsystemet-web package, which provides the ability to use the Designsystemet without React.
+description: Second prerelease of the @digdir/designsystemet-web package, which provides the ability to use Designsystemet without React.
 date: 2026-01-26
 author: Designsystemet
 imageSrc: /img/blog/ds-web-pre2.webp
@@ -83,4 +83,4 @@ If you discover errors, or have suggestions for improvements, you can create an
     'Tobias Barsnes',
     'Eirik Backer',
   ]}
-/>
+/>
diff --git a/apps/www/app/content/components/button/en/overview.mdx b/apps/www/app/content/components/button/en/overview.mdx
@@ -90,11 +90,11 @@ Buttons have an important function and are directly tied to an action. They give
 
 ### Button or link?
 
-Use button when the user should perform an action. Use a [link](/en/components/link/overview) when the user is navigated to a new URL.
+Use a button when the user should perform an action. Use a [link](/en/components/docs/link/overview) when the user is navigated to a new URL.
 
 #### Log in
 
-Use button when “Log in” actually logs the user in, for example by submitting a login form. Use a [link](/en/components/link/overview) when “Log in” sends the user to a login page or external authentication service.
+Use a button when “Log in” actually logs the user in, for example by submitting a login form. Use a [link](/en/components/docs/link/overview) when “Log in” sends the user to a login page or external authentication service.
 
 ### Button placement
 
diff --git a/apps/www/app/content/components/link/en/code.mdx b/apps/www/app/content/components/link/en/code.mdx
@@ -18,7 +18,7 @@ Sizes are controlled with [data-size](/en/fundamentals/code/sizes) and colors wi
 ```tsx
 import { Link } from '@digdir/designsystemet-react';
 
-<Link href='https://designsystemet.no/'>Go to the design system</Link>;
+<Link href='https://designsystemet.no/'>Go to Designsystemet</Link>;
 ```
 
 <ReactComponentDocs />
diff --git a/apps/www/app/content/components/link/en/overview.mdx b/apps/www/app/content/components/link/en/overview.mdx
@@ -42,7 +42,7 @@ It is important not to overuse links, as this can make it harder for users to fi
 Links are used when the user is navigated to a new URL, while buttons are used when an action should be performed.
 
 #### Log in
-Use a link when “Log in” sends the user to a login page or external authentication service. Use [button](/en/components/button/overview) when “Log in” actually logs the user in, for example by submitting a login form.
+Use a link when “Log in” sends the user to a login page or external authentication service. Use a [button](/en/components/docs/button/overview) when “Log in” actually logs the user in, for example by submitting a login form.
 
 ### Do not use an external link icon
 
diff --git a/apps/www/app/content/components/tabs/en/overview.mdx b/apps/www/app/content/components/tabs/en/overview.mdx
@@ -21,7 +21,7 @@ search_terms: sections, navigation, panels
 ### Icons only
 Tabs can be displayed with icons only for a more compact layout.  
 Ensure that the icons are intuitive and have descriptive titles for screen readers.  
-In the example below, we added a [tooltip](/en/components/docs/tooltip) to each tab to provide descriptive text for the icons.
+In the example below, we added a [tooltip](/en/components/docs/tooltip/overview) to each tab to provide descriptive text for the icons.
 
 <Story story="IconsOnlyEn" />
 
diff --git a/apps/www/app/content/components/tabs/no/overview.mdx b/apps/www/app/content/components/tabs/no/overview.mdx
@@ -21,7 +21,7 @@ search_terms: faner, seksjoner, seksjonar, navigasjon, panels
 ### Kun ikoner
 Tabs kan vises med bare ikoner for et mer kompakt utseende.
 Sørg for at ikonene er intuitive og har beskrivende titler for skjermlesere.
-I eksempelet under har vi lagt en [tooltip](/no/components/docs/tooltip) til hver fane for å gi beskrivende tekst til ikonene.
+I eksempelet under har vi lagt en [tooltip](/no/components/docs/tooltip/overview) til hver fane for å gi beskrivende tekst til ikonene.
 
 <Story story="IconsOnly" />
 
diff --git a/apps/www/app/content/fundamentals/en/code/css.mdx b/apps/www/app/content/fundamentals/en/code/css.mdx
@@ -71,7 +71,7 @@ Visually hides an element while still being accessible to screen readers.
 Preserves appearance, including background color, in print.
 
 ### `ds-focus` / `ds-focus--inset`
-Adds the design system focus ring around the element _when it gains focus with keyboard navigation_ (`:focus-visible`).
+Adds Designsystemet's focus ring around the element _when it gains focus with keyboard navigation_ (`:focus-visible`).
 
 ### `ds-focus--visible` / `ds-focus--visible--inset`
-Static "always-on" classes that add the design system focus ring around the element. <span className='ds-focus--visible'>Example.</span>
+Static "always-on" classes that add Designsystemet's focus ring around the element. <span className='ds-focus--visible'>Example.</span>
diff --git a/apps/www/app/content/fundamentals/en/code/react.mdx b/apps/www/app/content/fundamentals/en/code/react.mdx
@@ -91,5 +91,5 @@ import { Button } from '@digdir/designsystemet-react';
 
 ### Polyfill
 
-The design system uses [popover](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover) in some components. This api is classified as [Baseline: Newly available](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility) as of April 2024, when Firefox was the last browser to add it. In some cases, you may find that users are locked to older browser versions for various reasons, and then it may be appropriate to add a polyfill to ensure that `popover` works for everyone.
+Designsystemet uses [popover](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover) in some components. This api is classified as [Baseline: Newly available](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility) as of April 2024, when Firefox was the last browser to add it. In some cases, you may find that users are locked to older browser versions for various reasons, and then it may be appropriate to add a polyfill to ensure that `popover` works for everyone.
 * [Popover-Polyfill](https://github.com/oddbird/popover-polyfill)
diff --git a/apps/www/app/content/fundamentals/en/code/setup.mdx b/apps/www/app/content/fundamentals/en/code/setup.mdx
@@ -242,5 +242,5 @@ body {
 
 ## Polyfill
 
-The design system uses [popover](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover) in some components. This api is classified as [Baseline: Newly available](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility) as of April 2024, when Firefox was the last browser to add it. In some cases, you may find that users are locked to older browser versions for various reasons, and then it may be appropriate to add a polyfill to ensure that `popover` works for everyone.
+Designsystemet uses [popover](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover) in some components. This api is classified as [Baseline: Newly available](https://developer.mozilla.org/en-US/docs/Glossary/Baseline/Compatibility) as of April 2024, when Firefox was the last browser to add it. In some cases, you may find that users are locked to older browser versions for various reasons, and then it may be appropriate to add a polyfill to ensure that `popover` works for everyone.
 * [Popover-Polyfill](https://github.com/oddbird/popover-polyfill)
diff --git a/apps/www/app/content/fundamentals/no/code/css.mdx b/apps/www/app/content/fundamentals/no/code/css.mdx
@@ -70,7 +70,7 @@ Skjuler et element visuelt mens det fortsatt er tilgjengelig for skjermlesere.
 Bevarer utseende, inkludert bakgrunnsfarge, i print.
 
 ### `ds-focus` / `ds-focus--inset`
-Legger til designsystemets fokusring rundt elementet _når det får fokus med tastaturnavigering_ (`:focus-visible`).
+Legger til Designsystemets fokusring rundt elementet _når det får fokus med tastaturnavigering_ (`:focus-visible`).
 
 ### `ds-focus--visible` / `ds-focus--visible--inset`
-Statiske "alltid på" klasser som legger til designsystemets fokusring rundt elementet. <span className='ds-focus--visible'>Eksempel.</span>
+Statiske "alltid på" klasser som legger til Designsystemets fokusring rundt elementet. <span className='ds-focus--visible'>Eksempel.</span>
diff --git a/apps/www/app/content/fundamentals/no/theme/sizes-and-spacing.mdx b/apps/www/app/content/fundamentals/no/theme/sizes-and-spacing.mdx
@@ -13,7 +13,7 @@ search_terms: sizing, padding, margins, spacing, størrelsar, avstandar
 
 ## Komponentstørrelser
 
-De fleste komponentene i designsystemet finnes i tre anbefalte størrelser: `Small`, `Medium` og `Large` (`sm, md, lg`). 
+De fleste komponentene i Designsystemet finnes i tre anbefalte størrelser: `Small`, `Medium` og `Large` (`sm, md, lg`).
 Disse er utviklet for å tilpasse seg ulike behov på tvers av skjermstørrelser og bruksområder.
 <Image
   src='/img/component-size-buttons.png'
diff --git a/apps/www/app/content/intro/en/about-the-design-system.mdx b/apps/www/app/content/intro/en/about-the-design-system.mdx
@@ -1,7 +1,7 @@
 ---
 title: About Designsystemet
 sidebar_title: About Designsystemet
-description: Designsystemet provides core UI components and guidelines for coherent user experiences across services.
+description: Designsystemet provides core UI components and guidelines for coherent user experiences across services and organisations.
 date: 2026-01-07
 category: Introduction
 color: yellow
@@ -38,9 +38,9 @@ For most organisations, this means using Designsystemet as a shared foundation a
 
 
 <Card data-color='brand3' variant="tinted">
-    **230 organisations in the community**
+    **Over 300 organisations in the community**
 
-    More than 230 organisations (and 1,300+ people) are part of our community. Join us to learn, share, and help improve Designsystemet together. [Join the community](/en/intro/join-the-community)
+    Over 300 organisations and over 1,400 people are part of our community. Join us to learn, share, and help improve Designsystemet together. [Join the community](/en/intro/join-the-community)
 </Card>
 
 ## Why a shared design system?
@@ -110,42 +110,60 @@ Anyone building digital services can use Designsystemet. It’s open source, and
 
 ## Who uses Designsystemet today?
 
-Designsystemet is integrated into [Altinn Studio](https://altinn.studio/), used by over 70 agencies to build digital services. If you’re building services in Altinn Studio, you’re already using components from Designsystemet.
+Designsystemet is integrated into 700 applications through [Altinn Studio](https://altinn.studio/), where 80 different agencies build digital services. If you’re building services in Altinn Studio, you’re already using components from Designsystemet.
 
 Several other organizations also use Designsystemet in their services:
 
 <Card data-color='neutral'>
   <Details>
     <DetailsSummary>Examples of use</DetailsSummary>
     <DetailsContent>
-    - [Mattilsynet](https://design.mattilsynet.no/) builds its design system on top of Designsystemet.
-    - [Utdanningsdirektoratet](https://www.udir.no/) builds its design system on top of Designsystemet.
-    - Brønnøysundregistrene uses Designsystemet in, among others, [brreg.no](https://www.brreg.no/), [Business information](https://virksomhet.brreg.no/nb/oppslag/enheter), and the [Grants register](https://stotte.brreg.no/nb/oppslag/stoettetildeling).
-    - [Avinor](https://avinor.no/) uses Designsystemet in both internal professional systems and external public services. [Blog post about Avinor’s use of Designsystemet](/no/blog/avinor)
-    - [Enova](https://www.enova.no/) uses Designsystemet in several of its application solutions.
-    - [Innovation Norway](https://innovasjon.no/) builds its own design system on top of Designsystemet.
-    - [Norge.no](https://norge.no) uses Designsystemet.
-    - [Landbruksdirektoratet](https://www.landbruksdirektoratet.no/nb) builds its own design system on top of Designsystemet.
-    - [Byggforskserien](https://www.byggforsk.no/) builds its own design system on top of Designsystemet. 
-    - [Offentlig fagdag](https://offentligfagdag.no/) is built using Designsystemet.
-    - [The National Audit Office of Norway](https://www.riksrevisjonen.no/) builds its own design system on top of Designsystemet.
-    - [Lillestrøm municipality](https://www.lillestrom.kommune.no/) builds its own design system on top of Designsystemet.
-    - [Institute of Marine Research](https://www.hi.no/hi) builds its own design system on top of Designsystemet.
-    - [Norwegian Coastal Administration](https://www.kystverket.no/) builds its own design system on top of Designsystemet.
-    - [Norsk helsenett](https://www.nhn.no/) uses it directly in some of its digital solutions.
-    - [Huseierne](https://www.huseierne.no/) uses it directly in some of its digital solutions.
-    - [Data.norge.no](https://data.norge.no) uses Designsystemet.
-    - [NOBID ID](https://nobid.id/) uses Designsystemet.
-    - [Aibel](https://github.com/Aibel365/devops-designsystem) is building its own design system on top of Designsystemet.
-    - [Norwegian Red Cross](https://norwegianredcross.github.io/DesignSystem/#design) is building its own design system on top of Designsystemet.
-    - [BI](https://designsystem.bi.no) are using web elements from Designsystemet.
-    - [Skagerak Energi](https://www.npmjs.com/package/@skagerakenergi/skagerak-design-components) is building its own design system on top of Designsystemet.
-    - [Norwegian Customs](https://www.toll.no/) uses Designsystemet on its websites.
-    - [KS Digital](https://ksdigital.no) uses Designsystemet in, among others, [ledsagerbevis.no](https://ledsagerbevis.no/).
-    - [Statsforvalteren](https://github.com/Statsforvalteren/designsystemet-staf) uses Designsystemet.
-    - [Arbeidstilsynet](https://www.arbeidstilsynet.no/) uses Designsystemet on its websites.
-    - [UDI](https://www.udi.no/) is building its own design system on top of Designsystemet.
-    - [Digdir.no](https://www.digdir.no/), [the Equality and Anti-discrimination Ombud’s accessibility supervision](https://www.uutilsynet.no/), [UU status](https://uustatus.no/), and the [Collaboration portal](https://samarbeid.digdir.no/) use tokens from Designsystemet.
+**Building their own design systems on top of Designsystemet:**
+
+<br />
+
+- Aibel ([github.com/Aibel365](https://github.com/Aibel365/devops-designsystem))
+- BI ([npmjs.com/@bi-digital](https://www.npmjs.com/package/@bi-digital/react))
+- Institute of Marine Research ([npmjs.com/@havforsk](https://www.npmjs.com/package/@havforsk/react-components))
+- Helse Vest IKT ([Hviktor](https://github.com/HelseVestIKT/Hviktor))
+- Innovation Norway ([koble.innovasjonnorge.no](https://koble.innovasjonnorge.no/?path=/docs/introduction-hva-er-koble--docs))
+- KS Digital ([design.ksdigital.no](https://design.ksdigital.no/?path=/docs/03-angular_introduksjon--docs))
+- Norwegian Coastal Administration ([Styrbord](https://kystverket.github.io/styrbord/base/?path=/docs/readme--docs))
+- Landbruksdirektoratet
+- Lillestrøm municipality ([design.lillestrom.kommune.no](https://design.lillestrom.kommune.no/))
+- Mattilsynet ([design.mattilsynet.no](https://design.mattilsynet.no/))
+- The Norwegian Police IT Unit ([politiet.no/sherif](https://www.politiet.no/sheriff/?path=/docs/komponenter-popover--docs), uses some of Designsystemet's components as a starting point)
+- Norwegian Red Cross ([norwegianredcross.github.io](https://norwegianredcross.github.io/DesignSystem/#design))
+- Skagerak Energi ([npm.js](https://www.npmjs.com/package/@skagerakenergi/skagerak-design-components))
+- Statkraft's design system in Figma.
+- The National Audit Office of Norway
+- UDI ([Smudi](https://smudi.udi.no/))
+- Utdanningsdirektoratet ([design.udir.no](https://design.udir.no/))
+
+<Divider style={{ margin: 'var(--ds-size-8) 0' }} />
+
+**Using Designsystemet directly in solutions:**
+
+<br />
+
+- [Altinn](https://info.altinn.no/) uses Designsystemet.
+- [Arbeidstilsynet](https://www.arbeidstilsynet.no/) uses Designsystemet on its websites.
+- [Avinor](https://avinor.no/) uses Designsystemet in both internal professional systems and external public services. [Blog post about Avinor’s use of Designsystemet](/no/blog/avinor)
+- Brønnøysundregistrene uses Designsystemet in, among others, [brreg.no](https://www.brreg.no/), [Business information](https://virksomhet.brreg.no/nb/oppslag/enheter), and the [Grants register](https://stotte.brreg.no/nb/oppslag/stoettetildeling).
+- [Data.norge.no](https://data.norge.no) uses Designsystemet.
+- [Digitalt Dødsbo](https://info.altinn.no/skjemaoversikt/digitaliseringsdirektoratet/digitalt-dodsbo2/) uses Designsystemet.
+- [Departementenes digitaliseringsorganisasjon](https://github.com/dss-web/dio-designsystemet) uses Designsystemet.
+- [Digdir.no](https://www.digdir.no/), [the Equality and Anti-discrimination Ombud’s accessibility supervision](https://www.uutilsynet.no/), [UU status](https://uustatus.no/), and the [Collaboration portal](https://samarbeid.digdir.no/) use tokens from Designsystemet.
+- [Enova](https://www.enova.no/) uses Designsystemet in several of its application solutions.
+- [Huseierne](https://www.huseierne.no/) uses it directly in some of its digital solutions.
+- [NOBID ID](https://nobid.id/) uses Designsystemet.
+- [Norge.no](https://norge.no) uses Designsystemet.
+- [Norsk helsenett](https://www.nhn.no/) uses it directly in some of its digital solutions.
+- [Norwegian Customs](https://www.toll.no/) uses Designsystemet on its websites.
+- [Offentlig fagdag](https://offentligfagdag.no/) is built using Designsystemet.
+- [Statsforvalteren](https://github.com/Statsforvalteren/designsystemet-staf) uses Designsystemet.
+- Trøndelag County Municipality uses Designsystemet in some of its digital solutions.
+- Vestfold county, student follow-up
 
 <br/>
 
diff --git a/apps/www/app/content/intro/en/join-the-community.mdx b/apps/www/app/content/intro/en/join-the-community.mdx
@@ -14,7 +14,7 @@ import { Chat2Icon } from '@navikt/aksel-icons';
 
 Designsystemet aims to foster an active and inclusive community where everyone is welcome to contribute, share experiences, and learn from one another. Participation is entirely voluntary, both in how and how much you take part, and you can follow along without contributing actively.
 
-Join the community to stay informed about updates and receive invitations to events and demos. The easiest way to take part is through our open Slack. More than 230 organisations and over 1,300 people have already joined.
+Join the community to stay informed about updates and receive invitations to events and demos. The easiest way to take part is through our open Slack. Over 300 organisations and over 1,400 people have already joined.
 
 <Card data-color='success' variant="tinted" asChild>
   <Link href='https://designsystemet.no/slack' style={{ color:'var(--ds-color-success-text-default)', textDecoration: 'underline' }}>
@@ -84,4 +84,3 @@ Do you have experiences you would like to share? This could be anything from how
 ---
 
 Do you have feedback or thoughts you would like to share? Want to be more closely involved in the collaboration? Send us an email at [designsystem@digdir.no](mailto:designsystem@digdir.no). All input is welcome.
-
diff --git a/apps/www/app/content/intro/no/about-the-design-system.mdx b/apps/www/app/content/intro/no/about-the-design-system.mdx
diff --git a/apps/www/app/content/intro/no/join-the-community.mdx b/apps/www/app/content/intro/no/join-the-community.mdx
diff --git a/apps/www/app/locales/no.ts b/apps/www/app/locales/no.ts
