diff --git a/documentation/guides/getting-started.md b/documentation/guides/getting-started.md
index 7b81df2d5..819ad244a 100644
--- a/documentation/guides/getting-started.md
+++ b/documentation/guides/getting-started.md
@@ -2,7 +2,7 @@
 
 ## Try Solid
 
-By far the easiest way to get started with Solid is to try it online. Our REPL at https://playground.solidjs.com is the perfect way to try out ideas. As is https://codesandbox.io/ where you can modify any of our [examples](../resources/examples.md).
+By far the easiest way to get started with Solid is to try it online. Our REPL at https://playground.solidjs.com is the perfect way to try out ideas. As is https://codesandbox.io/ where you can modify any of our Examples.
 
 Alternatively, you can use our simple [Vite](https://vitejs.dev/) templates by runnings these commands in your terminal:
 
@@ -49,9 +49,7 @@ const [last, setLast] = createSignal("Bourne");
 createEffect(() => console.log(`${first()} ${last()}`))
 ```
 
-You can learn more about [Solid's Reactivity](reactivity.md) and [Solid's Rendering](rendering.md).
-
-You can also view our full [API Reference](../api.md).
+You can learn more in the Reactivity and Rendering sections.
 
 ## Think Solid
 
@@ -83,7 +81,7 @@ Solid has a dynamic server side rendering solution that enables a truly isomorph
 
 Since Solid supports asynchronous and streaming rendering on the server, you get to write your code one way and have it execute on the server. This means that features like [render-as-you-fetch](https://reactjs.org/docs/concurrent-mode-suspense.html#approach-3-render-as-you-fetch-using-suspense) and code splitting just work in Solid.
 
-For more information, read the [SSR guide](./server.md).
+For more information, read the Server guide.
 
 ## No Compilation?
 
diff --git a/documentation/guides/server.md b/documentation/guides/server.md
index a95adaa5b..e181aea7e 100644
--- a/documentation/guides/server.md
+++ b/documentation/guides/server.md
@@ -122,6 +122,8 @@ Solid's Isomorphic SSR solution is very powerful in that you can write your code
 
 We use markers rendered in the server to match elements and resource locations on server. For this reason the Client and Server should have the same components. This is not typically a problem given that Solid renders the same way on client and server. But currently there is no means to render something on the server that does not get hydrated on the client. Currently, there is no way to partially hydrate a whole page, and not generate hydration markers for it. It is all or nothing. Partial Hydration is something we want to explore in the future.
 
+Finally, all resources need to be defined under the `render` tree. They are automatically serialized and picked up in the browser, but that works because the `render` or `pipeTo` methods keep track of the progress of the render. Something we cannot do if they are created in isolated context. Similarly there is no reactivity on the server so do not update signals on initial render and expect them to reflect higher up the tree. While we have Suspense boundaries Solid's SSR is basically top down.
+
 ## Getting Started with SSR
 
 SSR configurations are tricky. We have a few examples in the [solid-ssr](https://github.com/solidjs/solid/blob/main/packages/solid-ssr) package.