Remove instructions about actions in useSubmission(s) reference

src/routes/solid-router/reference/data-apis/use-submission.mdx

@@ -24,20 +24,11 @@ function Component() {
 }
 ```
 
-## Creating the action
+<Callout type="info>
 
-The Action which will trigger the submission should be created with the [`action()`](/solid-router/reference/data-apis/action) helper and, when in a [SolidStart](/solid-start) app, it is recommended to leverage the `"use server"` directive to leverage the caching and RPC capabilities from the server-side.
+Learn more about actions in the [`action`](/solid-router/reference/data-apis/action) docs.
 
-```tsx title="/component.tsx" {1,3-4}
-import { action } from "@solidjs/router";
-
-const postNameAction = action(() => {
-  "use server";
-  /*... logic ...*/ 
-  return { data: "Hello SolidStart" };
-})
-
-```
+</Callout>
 
 ## Filtering Submissions
 

src/routes/solid-router/reference/data-apis/use-submissions.mdx

@@ -42,20 +42,13 @@ function Component() {
 }
 ```
 
-## Creating the action
+<Callout type="info">
 
-The Action which will trigger the submission should be created with the [`action()`](/solid-router/reference/data-apis/action) helper and, when in a [SolidStart](/solid-start) app. If in a [SolidStart](/solid-start) app to leverage the caching and RPC capabilities from the server-side.
+To trigger a submission, [actions](https://docs.solidjs.com/) can be used.
 
-```tsx title="/component.tsx" {1,3-4}
-import { action } from "@solidjs/router";
+ As a note, if building a SolidStart app, it's recommended to utilize the `"use server"` directive to take advantage of server-side caching and RPC capabilities.
 
-const postNameAction = action(() => {
-  "use server";
-  /*... logic ...*/ 
-  return { data: "Hello SolidStart" };
-})
-
-```
+</Callout>
 
 ## Filtering Submissions
 
@@ -202,4 +195,4 @@ function Component() {
       </form>
     )
 }
-```
+```