[Doc] A few minor updates (#6098)

* Tutorial: add a note about downloading the schema from the IDE plugin

* ApolloStore: add a note about read/write operations being synchronous

* Add a Java hint in the Getting Started section

* Fix <Note> missing new lines

* Rename index.md to index.mdx so <Tip> works

Author: BoD

docs/source/advanced/client-awareness.mdx

@@ -16,5 +16,7 @@ val apolloClient = ApolloClient.Builder()
 ```
 
 <Note>
+
 This example uses `BuildConfig` to set the app's `applicationId` as the client name and its `versionName` as the client version, but you can override this. Especially, if your iOS and Android apps use the same package name, it's useful to customize it to be able to differentiate the clients.
+
 </Note>

docs/source/advanced/nullability.mdx

@@ -247,7 +247,9 @@ class User(
 ```
 
 <Note>
+
 The error is thrown during parsing but still caught before it reaches your UI code. If no parent field catches it, the Apollo Kotlin runtime will and set it as `ApolloResponse.exception`. 
+
 </Note>  
 
 ### Coerce errors to null
@@ -276,7 +278,9 @@ class User(
 ```
 
 <Note>
+
 The error is thrown during parsing but still caught before it reaches your UI code. If no parent field catches it, the Apollo Kotlin runtime does and exposes the exception in `ApolloResponse.exception`. 
+
 </Note>  
 
 ## `@catchByDefault`
@@ -317,4 +321,4 @@ In order to change that default to "opt-in the errors you want to handle", you c
 1. Add `@catch` to individual fields, get more comfortable with how it works.
 1. When ready to do the big switch, change to `extend schema catch(to: THROW)` and (at the same time) add  `query GetFoo @catch(to: NULL) {}` on all operations/fragments (this is a no-op).
 1. From this moment on, new queries written are `catch(to: THROW)` by default.
-1. Remove `query GetFoo @catch(to: NULL) {}` progressively.
+1. Remove `query GetFoo @catch(to: NULL) {}` progressively.

docs/source/caching/store.mdx

@@ -15,6 +15,9 @@ val apolloClient = ApolloClient.Builder()
 val apolloStore: ApolloStore = apolloClient.apolloStore
 ```
 
+Note that the read and write operations are synchronous and might block if the underlying cache is doing IO (such as the [SQLite cache](../caching/normalized-cache#sqlite-cache)).
+Therefore calling them from the main thread should be avoided.
+
 ## Reading operation data
 
 Just like a regular GraphQL query, the main way to use the store is to read and write queries:

docs/source/index.md renamed to docs/source/index.mdx

@@ -61,6 +61,12 @@ apollo {
 }
 ```
 
+<Tip>
+
+Using Java? Apollo Kotlin has a dedicated [Java Support](https://apollographql.github.io/apollo-kotlin-java-support/) repository.
+
+</Tip>
+
 Apollo Kotlin supports three types of files:
 - `.graphqls` schema files: describes the types in your backend using the GraphQL syntax.
 - `.json` schema files: describes the types in your backend using the Json syntax.

docs/source/tutorial/02-add-the-graphql-schema.mdx

@@ -46,4 +46,6 @@ Then, from the root of the project, run this command in Android Studio's Termina
 
 This will download a `schema.graphqls` file from your endpoint to `app/src/main/graphql/schema.graphqls`.
 
+If you installed the [Android Studio Plugin](https://www.apollographql.com/docs/kotlin/testing/android-studio-plugin/), you can also download the schema from <kbd>Tools</kbd> | <kbd>Apollo</kbd> | <kbd>Download Schema</kbd>.
+
 Next, [write your first query](03-write-your-first-query) that uses this schema.