docs: small improvements

- add callout for note in bind
- change cautions in tutorials to infos
- add links to React and RxJS in tutorials
- grammar in core concepts

Author: rikoe

docs/api/core/bind.md

@@ -26,8 +26,10 @@ function bind<T>(
 2. The shared Observable that the hook uses: It also replays back the latest
    value emitted. It can be used for composing other streams that depend on it.
 
-Note that bind doesn't propagate completions from the source stream - The shared
+:::note
+`bind` doesn't propagate completions from the source stream - the shared
 subscription is closed as soon as there are no subscribers to that Observable.
+:::
 
 ### Example
 

docs/core-concepts.md

@@ -127,7 +127,7 @@ For this reason, it's important to understand that these streams only represent
 
 If you want to keep one of these streams alive for as long as you need, React-RxJS also exposes `useSubscribe(stream)` and `<Subscribe source$={stream}>{ content }</Subscribe>`, which will render `{ content }` only after it subscribed to `stream`.
 
-With the mental model of streams as a state, it's also worth noting that the observables returned by `bind` don't complete: If the source of that observable completes, it will keep the last value and replay it back to new subscribers, as a completion on the source means that there won't be more changes to that stream. Remember that if the subscriber count reaches 0, this state will be cleaned off and the subscription will restart when a new observer subscribes later on.
+With the mental model of "streams as state", it's also worth noting that the observables returned by `bind` won't complete: If the source of that observable completes, it will keep the last value and replay it back to new subscribers, as a completion on the source means that there won't be more changes to that stream. Remember that if the subscriber count reaches 0, this state will be cleaned up, and the subscription will restart when a new observer subscribes later on.
 
 ## Composing streams
 

docs/tutorial/github-issues.md

@@ -4,12 +4,14 @@ title: Github Issues Viewer
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-:::caution
-This tutorial assumes you are already familiar with both RxJS and React.
+:::info Note
+This tutorial assumes you are already familiar with both [RxJS](https://rxjs.dev) 
+and [React](https://reactjs.org).
 :::
 
-For this tutorial we will be borrowing the [Github issues example that is taught
-in the Advanced Tutorial of the Redux Toolkit](https://redux-toolkit.js.org/tutorials/advanced-tutorial).
+For this tutorial we will be borrowing the Github issues example that is taught
+in the [Advanced Tutorial](https://redux-toolkit.js.org/tutorials/advanced-tutorial) 
+of the [Redux Toolkit](https://redux-toolkit.js.org).
 
 It's a great example because it starts with a plain React application and it then
 shows how to migrate that application to Redux using the Redux Toolkit (RTK). One of the many good

docs/tutorial/todos.md

@@ -2,9 +2,9 @@
 title: Todo App
 ---
 
-:::caution
+:::info Note
 This tutorial assumes you have gone through the [Github Issues Viewer](/docs/tutorial/github-issues) 
-tutorial, and that you are already familiar with both RxJS and React.
+tutorial, and that you are already familiar with both [RxJS](https://rxjs.dev) and [React](https://reactjs.org).
 :::
 
 The purpose of the tutorial is to introduce the most important APIs of the