Merge pull request #10147 from rex4539/typos

Fix typos

docs/architecture-decisions/adr006-avoid-react-fc.md

@@ -45,7 +45,7 @@ const GoodComponent = ({ text, children }: GoodProps) => (
   </div>
 );
 
-/* Or as a shorthand, if no specifc child type is required */
+/* Or as a shorthand, if no specific child type is required */
 type GoodProps = PropsWithChildren<{ text: string }>;
 const GoodComponent = ({ text, children }: GoodProps) => (
   <div>

docs/assets/search/architecture.drawio.svg

@@ -525,7 +525,7 @@
                     </div>
                 </foreignObject>
                 <text x="491" y="557" fill="#5C5C5C" font-family="Helvetica" font-size="9px" text-anchor="middle">
-                    Compile and Execut...
+                    Compile and Execute...
                 </text>
             </switch>
         </g>

docs/features/kubernetes/configuration.md

@@ -255,7 +255,7 @@ CPU/Memory for pods returned by the API server. Defaults to `false`.
 
 ##### `exposeDashboard`
 
-This determines wether the `dashboardApp` and `dashboardParameters` should be
+This determines whether the `dashboardApp` and `dashboardParameters` should be
 automatically configured in order to expose the GKE dashboard from the
 Kubernetes plugin.
 

docs/features/software-templates/writing-templates.md

@@ -251,7 +251,7 @@ use `ui:widget: password` or set some properties of `ui:backstage`:
       type: string
       ui:backstage:
         review:
-          show: false # wont print any info about 'hidden' property on Review Step
+          show: false # won't print any info about 'hidden' property on Review Step
 ```
 
 ### Remove sections or fields based on feature flags

docs/local-dev/cli-build-system.md

@@ -66,7 +66,7 @@ These steps are generally kept isolated form each other, with each step focusing
 on its specific task. For example, we do not do linting or type checking
 together with the building or bundling. This is so that we can provide more
 flexibility and avoid duplicate work, improving performance. It is strongly
-recommended that as a part of developing withing Backstage you use a code editor
+recommended that as a part of developing within Backstage you use a code editor
 or IDE that has support for formatting, linting, and type checking.
 
 Let's dive into a detailed look at each of these steps and how they are