Merge branch 'main' of https://github.com/navikt/aksel

Author: KenAJoh

.storybook/docs/PilotsIntro.mdx

@@ -9,27 +9,26 @@ We are looking for teams wanting to test our new theming implementation and dark
 ## What is a pilot team?
 
 - A pilot team is a team that tests new implementations before they are released.
-- The team will test the new implementation in a real-world scenario and provide feedback us with feedback.
+- The team will test the new implementation in a real-world scenario and provide us with feedback.
 - The feedback will be used to improve the implementation before it replaces the old system.
 
 As a pilot team, we want close communication to get
 feedback on the changes. We want to know all the unclear and bad parts
-of our implementations, so that we can improve them incrementally before the big release.
+of our implementations, so that we can fix them all up before the big release.
 
 ## Who are we mainly looking for?
 
 We are focusing on applications meant for our internal systems and services for now. This line is often a little blurry,
-but can be categorized as all applications using "Dekoratøren" will not be considered internal.
+but in short, all the public facing applications including those using "Dekoratøren" will not be considered internal.
 Support for "Dekoratøren" is quite far down the road at the moment.
 
 For teams wanting to test the new implementation, there are some key points to consider:
 
-- They might be in the early stages of developing a new product or service.
-- They are able to test either design tokens, darkmode, updated CSS or a combination of these.
-- Have the capacity to test and provide feedback on the new implementation.
+- You _probably_ want to be in the earlier stages of developing a new product or service (to more easily test something in isolation).
+- You can test _any_ smaller subset of the new system as it's not an "all or nothing" ordeal. This could be: design tokens, darkmode, updated CSS or a combination of these.
+- You have the capacity to test and provide feedback on the new implementation (You'll be saving Nav countless hours for every hour spent!).
 
-Everyone is welcome to test the new implementation, but for some larger applications, it might be a bit early to adopt the new system.
-There might be breaking changes as we go,
+Everyone is welcome to test the new implementation, but for some larger applications, it might be a bit early to adopt the new system. Keep in mind that there might be breaking changes as we go,
 and we won't have all tooling ready for adoption yet so you might have to do some manual work.
 
 ## How to give feedback