docs: make server-side batching the default import method

Restructure the batch-import guide so server-side (automatic) batching is the
first and recommended way to import data, instead of a separate feature section:

- Lead with server-side batching; present client-side batching as "Manual
  batching", the alternative for manual control or for the Go client.
- The Go tab points to manual batching (the Go client has no server-side
  batching API) instead of "coming soon".
- Note that server-side batching uses the gRPC API (enabled by default).
- concepts/data-import.mdx: correct the now-stale "only the Python client
  supports server-side batch imports" (now Python, TypeScript, Java, and C#;
  Go does not yet), and fix a broken sentence.

Author: g-despot

docs/weaviate/concepts/data-import.mdx

@@ -19,7 +19,7 @@ Weaviate offers two flexible methods for importing data in bulk: **client-side b
 
 :::tip
 
-For **code examples**, check out the [How-to: Batch import](../manage-objects/import.mdx) guide. Currently, only the Python client supports server-side batch imports.
+For **code examples**, check out the [How-to: Batch import](../manage-objects/import.mdx) guide. Server-side batch imports are supported by the Python, TypeScript, Java, and C# clients. The Go client does not yet support them; use client-side batching instead.
 
 :::
 
@@ -40,7 +40,7 @@ Weaviate's server-side batching, also known as **automatic batching**, aims to p
 When an automatic batch import is initiated, the client opens a persistent connection to the server for the duration of the batch job.
 
 - **Client sends data**: Your client sends objects to the server in chunks, at a rate that is based on server-provided feedback.
-- **Server manages queues**: The server places incoming objects into an internal. The queue is decoupled the network communication from the actual database ingestion (like vectorization and storage).
+- **Server manages queues**: The server places incoming objects into an internal queue. This queue decouples the network communication from the actual database ingestion (like vectorization and storage).
 - **Dynamic backpressure**: The server continuously monitors its internal queue size. It calculates an exponential moving average (EMA) of its workload and tells the client the ideal number of objects to send in the next chunk. This feedback loop allows the system to self-regulate, maximizing throughput without overwhelming the server.
 - **Asynchronous errors**: If an error occurs while processing an object (e.g., validation fails), the server sends the error message back to the client over a separate, dedicated stream without interrupting the flow of objects.
 

docs/weaviate/manage-objects/import.mdx

@@ -17,122 +17,122 @@ import CSharpCode from '!!raw-loader!/_includes/code/csharp/ManageObjectsImportT
 import GoCode from '!!raw-loader!/_includes/code/howto/go/docs/manage-data.import_test.go';
 import SkipLink from '/src/components/SkipValidationLink'
 
-[Batch imports](../tutorials/import.mdx) are an efficient way to add multiple data objects and cross-references.
+[Batch imports](../tutorials/import.mdx) are an efficient way to add multiple data objects and cross-references. For most use cases, we recommend **server-side batching** as the starting point: the server tells the client how much data to send next, so you don't have to tune batch parameters yourself. When you need manual control over the batch size and concurrency — or you are using a client that does not yet support server-side batching — use [manual batching](#manual-batching) instead.
 
-<details>
-  <summary>Additional information</summary>
-
-To create a bulk import job, follow these steps:
+## Server-side batching
 
-1. Initialize a batch object.
-1. Add items to the batch object.
-1. Ensure that the last batch is sent (flushed).
+import SsbStatus from '/_includes/feature-notes/ssb-status.mdx';
 
-</details>
+<SsbStatus/>
 
-## Basic import
+With [server-side batch imports](../concepts/data-import.mdx#server-side-batching) (also called "automatic" batching), the client sends data in batch sizes determined by feedback from the server. This simplifies your code and helps the server manage its own load. The following example adds objects to a collection named `MyCollection`.
 
-The following example adds objects to the `MyCollection` collection.
+Server-side batching uses the [gRPC API](#use-the-grpc-api), which current client versions enable by default.
 
 <Tabs className="code" groupId="languages">
   <TabItem value="py" label="Python">
     <FilteredTextBlock
       text={PyCode}
-      startMarker="# START BasicBatchImportExample"
-      endMarker="# END BasicBatchImportExample"
+      startMarker="# START ServerSideBatchImportExample"
+      endMarker="# END ServerSideBatchImportExample"
       language="py"
     />
-
-### Error handling
-
-<!-- TODO[g-despot]: Add link to external Python references once created for "reference page" -->
-
-During a batch import, any failed objects or references will be stored and can be obtained through `batch.failed_objects` and `batch.failed_references`.
-Additionally, a running count of failed objects and references is maintained and can be accessed through `batch.number_errors` within the context manager.
-This counter can be used to stop the import process in order to investigate the failed objects or references.
-
-Find out more about error handling on the Python client [reference page](/weaviate/client-libraries/python).
-
   </TabItem>
   <TabItem value="ts" label="JavaScript/TypeScript">
     <FilteredTextBlock
       text={TSCode}
-      startMarker="// START BasicBatchImportExample"
-      endMarker="// END BasicBatchImportExample"
+      startMarker="// START ServerSideBatchImportExample"
+      endMarker="// END ServerSideBatchImportExample"
       language="ts"
     />
   </TabItem>
   <TabItem value="go" label="Go">
-    <FilteredTextBlock
-      text={GoCode}
-      startMarker="// START BasicBatchImportExample"
-      endMarker="// END BasicBatchImportExample"
-      language="go"
-    />
+
+The Go client does not support server-side batching; use [manual batching](#manual-batching) instead.
+
   </TabItem>
   <TabItem value="java" label="Java">
     <FilteredTextBlock
       text={JavaV6Code}
-      startMarker="// START BasicBatchImportExample"
-      endMarker="// END BasicBatchImportExample"
+      startMarker="// START ServerSideBatchImportExample"
+      endMarker="// END ServerSideBatchImportExample"
       language="java"
     />
   </TabItem>
   <TabItem value="csharp" label="C#">
     <FilteredTextBlock
       text={CSharpCode}
-      startMarker="// START BasicBatchImportExample"
-      endMarker="// END BasicBatchImportExample"
+      startMarker="// START ServerSideBatchImportExample"
+      endMarker="// END ServerSideBatchImportExample"
       language="csharp"
     />
   </TabItem>
 </Tabs>
 
-## Server-side batching
+## Manual batching
 
-import SsbStatus from '/_includes/feature-notes/ssb-status.mdx';
+Use manual (client-side) batching when you want to control the batch size and concurrency yourself, or when using a client that does not yet support server-side batching (such as the Go client). The following example adds objects to the `MyCollection` collection.
 
-<SsbStatus/>
+<details>
+  <summary>Additional information</summary>
+
+To create a bulk import job manually, follow these steps:
+
+1. Initialize a batch object.
+1. Add items to the batch object.
+1. Ensure that the last batch is sent (flushed).
 
-Here's how to import objects into a collection named `MyCollection` using [server-side batch imports](../concepts/data-import.mdx#server-side-batching). The client will send data in batch sizes using feedback from the server.
+</details>
 
 <Tabs className="code" groupId="languages">
   <TabItem value="py" label="Python">
     <FilteredTextBlock
       text={PyCode}
-      startMarker="# START ServerSideBatchImportExample"
-      endMarker="# END ServerSideBatchImportExample"
+      startMarker="# START BasicBatchImportExample"
+      endMarker="# END BasicBatchImportExample"
       language="py"
     />
+
+### Error handling
+
+<!-- TODO[g-despot]: Add link to external Python references once created for "reference page" -->
+
+During a batch import, any failed objects or references will be stored and can be obtained through `batch.failed_objects` and `batch.failed_references`.
+Additionally, a running count of failed objects and references is maintained and can be accessed through `batch.number_errors` within the context manager.
+This counter can be used to stop the import process in order to investigate the failed objects or references.
+
+Find out more about error handling on the Python client [reference page](/weaviate/client-libraries/python).
+
   </TabItem>
   <TabItem value="ts" label="JavaScript/TypeScript">
     <FilteredTextBlock
       text={TSCode}
-      startMarker="// START ServerSideBatchImportExample"
-      endMarker="// END ServerSideBatchImportExample"
+      startMarker="// START BasicBatchImportExample"
+      endMarker="// END BasicBatchImportExample"
       language="ts"
     />
   </TabItem>
-    <TabItem value="go" label="Go">
-
-```go
-// Go support coming soon
-```
-
+  <TabItem value="go" label="Go">
+    <FilteredTextBlock
+      text={GoCode}
+      startMarker="// START BasicBatchImportExample"
+      endMarker="// END BasicBatchImportExample"
+      language="go"
+    />
   </TabItem>
   <TabItem value="java" label="Java">
     <FilteredTextBlock
       text={JavaV6Code}
-      startMarker="// START ServerSideBatchImportExample"
-      endMarker="// END ServerSideBatchImportExample"
+      startMarker="// START BasicBatchImportExample"
+      endMarker="// END BasicBatchImportExample"
       language="java"
     />
   </TabItem>
   <TabItem value="csharp" label="C#">
     <FilteredTextBlock
       text={CSharpCode}
-      startMarker="// START ServerSideBatchImportExample"
-      endMarker="// END ServerSideBatchImportExample"
+      startMarker="// START BasicBatchImportExample"
+      endMarker="// END BasicBatchImportExample"
       language="csharp"
     />
   </TabItem>
@@ -171,7 +171,7 @@ The Java client v6 uses gRPC by default.
 
 To use the gRPC API with the Go client, add the `GrpcConfig` field to your client connection code. Update `Secured` if you use an encrypted connection.<br/><br/>
 
-```java
+```go
 cfg := weaviate.Config{
   Host:   fmt.Sprintf("localhost:%v", "8080"),
   Scheme: "http",