Merge pull request #114013 from SnehaGunda/tabbedconceptual

Adding tabs

Author: PRMerger18

articles/cosmos-db/cassandra-change-feed.md

@@ -17,6 +17,8 @@ The following example shows how to get a change feed on all the rows in a Cassan
 
 In each iteration, the query resumes at the last point changes were read, using paging state. We can see a continuous stream of new changes to the table in the Keyspace. We will see changes to rows that are inserted, or updated. Watching for delete operations using change feed in Cassandra API is currently not supported.
 
+# [C#](#tab/csharp)
+
 ```C#
     //set initial start time for pulling the change feed
      DateTime timeBegin = DateTime.UtcNow;
@@ -65,6 +67,9 @@ In each iteration, the query resumes at the last point changes were read, using
     }
 
 ```
+
+# [Java](#tab/java)
+
 ```java
         Session cassandraSession = utils.getSession();
 
@@ -99,19 +104,27 @@ In each iteration, the query resumes at the last point changes were read, using
         }
 
 ```
+---
+
 In order to get the changes to a single row by primary key, you can add the primary key in the query. The following example shows how to track changes for the row where "user_id = 1"
 
+# [C#](#tab/csharp)
+
 ```C#
     //Return the latest change for all row in 'user' table where user_id = 1
     IStatement changeFeedQueryStatement = new SimpleStatement(
     $"SELECT * FROM uprofile.user where user_id = 1 AND COSMOS_CHANGEFEED_START_TIME() = '{timeBegin.ToString("yyyy-MM-ddTHH:mm:ss.fffZ", CultureInfo.InvariantCulture)}'");
 
 ```
+
+# [Java](#tab/java)
+
 ```java
     String query="SELECT * FROM uprofile.user where user_id=1 and COSMOS_CHANGEFEED_START_TIME()='" 
            			+ dtf.format(now)+ "'";
     SimpleStatement st=new  SimpleStatement(query);
 ```
+---
 ## Current limitations
 
 The following limitations are applicable when using change feed with Cassandra API:

articles/cosmos-db/create-sql-api-java-changefeed.md

@@ -86,7 +86,6 @@ mvn clean package
 
    # [Java SDK 4.0](#tab/v4sdk)
 
-    **Java SDK 4.0**
     ```java
     changeFeedProcessorInstance = getChangeFeedProcessor("SampleHost_1", feedContainer, leaseContainer);
     changeFeedProcessorInstance.start()
@@ -101,7 +100,6 @@ mvn clean package
 
    # [Java SDK 3.7.0](#tab/v3sdk)
 
-    **Java SDK 3.7.0**
     ```java
     changeFeedProcessorInstance = getChangeFeedProcessor("SampleHost_1", feedContainer, leaseContainer);
     changeFeedProcessorInstance.start()
@@ -114,7 +112,7 @@ mvn clean package
     while (!isProcessorRunning.get()); //Wait for Change Feed processor start    
     ```
    ---
-   
+
     ```"SampleHost_1"``` is the name of the Change Feed processor worker. ```changeFeedProcessorInstance.start()``` is what actually starts the Change Feed processor.
 
     Return to the Azure Portal Data Explorer in your browser. Under the **InventoryContainer-leases** container, click **items** to see its contents. You will see that Change Feed Processor has populated the lease container, i.e. the processor has assigned the ```SampleHost_1``` worker a lease on some partitions of the **InventoryContainer**.
@@ -125,7 +123,6 @@ mvn clean package
 
    # [Java SDK 4.0](#tab/v4sdk)
 
-    **Java SDK 4.0**
     ```java
     public static ChangeFeedProcessor getChangeFeedProcessor(String hostName, CosmosAsyncContainer feedContainer, CosmosAsyncContainer leaseContainer) {
         ChangeFeedProcessorOptions cfOptions = new ChangeFeedProcessorOptions();
@@ -153,7 +150,6 @@ mvn clean package
 
    # [Java SDK 3.7.0](#tab/v3sdk)
 
-    **Java SDK 3.7.0**
     ```java
     public static ChangeFeedProcessor getChangeFeedProcessor(String hostName, CosmosContainer feedContainer, CosmosContainer leaseContainer) {
         ChangeFeedProcessorOptions cfOptions = new ChangeFeedProcessorOptions();
@@ -196,7 +192,6 @@ mvn clean package
     
    # [Java SDK 4.0](#tab/v4sdk)
 
-    **Java SDK 4.0**
     ```java
     public static void deleteDocument() {
 
@@ -225,7 +220,6 @@ mvn clean package
     ```
    # [Java SDK 3.7.0](#tab/v3sdk)
 
-    **Java SDK 3.7.0**
     ```java
     public static void deleteDocument() {
 

articles/cosmos-db/mongodb-change-streams.md

@@ -40,7 +40,7 @@ The following error codes and messages are supported when using change streams:
 
 The following example shows how to get change streams on all the items in the collection. This example creates a cursor to watch items when they are inserted, updated, or replaced. The `$match` stage, `$project` stage, and `fullDocument` option are required to get the change streams. Watching for delete operations using change streams is currently not supported. As a workaround, you can add a soft marker on the items that are being deleted. For example, you can add an attribute in the item called "deleted." When you'd like to delete the item, you can set "deleted" to `true` and set a TTL on the item. Since updating "deleted" to `true` is an update, this change will be visible in the change stream.
 
-### JavaScript:
+# [JavaScript](#tab/javascript)
 
 ```javascript
 var cursor = db.coll.watch(
@@ -56,8 +56,7 @@ while (!cursor.isExhausted()) {
     }
 }
 ```
-
-### C#:
+# [C#](#tab/csharp)
 
 ```csharp
 var pipeline = new EmptyPipelineDefinition<ChangeStreamDocument<BsonDocument>>()