Improve docs on optimistic concurrency and tokens

.openpublishing.redirection.json

@@ -469,6 +469,11 @@
             "source_path": "entity-framework/core/querying/raw-sql.md",
             "redirect_url": "/ef/core/querying/sql-queries",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "entity-framework/core/modeling/concurrency.md",
+            "redirect_url": "/ef/core/saving/concurrency",
+            "redirect_document_id": false
         }
     ]
 }

entity-framework/core/managing-schemas/scaffolding/index.md

@@ -151,7 +151,7 @@ Finally, the model is used to generate code. The corresponding entity type class
 
 - Not everything about a model can be represented using a database schema. For example, information about [**inheritance hierarchies**](xref:core/modeling/inheritance), [**owned types**](xref:core/modeling/owned-entities), and [**table splitting**](xref:core/modeling/table-splitting) are not present in the database schema. Because of this, these constructs will never be reverse engineered.
 - In addition, **some column types** may not be supported by the EF Core provider. These columns won't be included in the model.
-- You can define [**concurrency tokens**](xref:core/modeling/concurrency), in an EF Core model to prevent two users from updating the same entity at the same time. Some databases have a special type to represent this type of column (for example, rowversion in SQL Server) in which case we can reverse engineer this information; however, other concurrency tokens will not be reverse engineered.
+- You can define [**concurrency tokens**](xref:core/saving/concurrency) in an EF Core model to prevent two users from updating the same entity at the same time. Some databases have a special type to represent this type of column (for example, rowversion in SQL Server) in which case we can reverse engineer this information; however, other concurrency tokens will not be reverse engineered.
 - Prior to EF Core 6, [the C# 8 nullable reference type feature](/dotnet/csharp/tutorials/nullable-reference-types) wasn't supported in reverse engineering: EF Core always generated C# code that assumed the feature is disabled. For example, nullable text columns were scaffolded as a property with type `string` , not `string?`, with either the Fluent API or Data Annotations used to configure whether a property is required or not. If using an older version of EF Core, you can still edit the scaffolded code and replace these with C# nullability annotations.
 
 ## Customizing the model

entity-framework/core/providers/cosmos/index.md

@@ -313,7 +313,7 @@ This is the resulting JSON:
 > [!NOTE]
 > Support for eTag concurrency was introduced in EF Core 5.0.
 
-To configure an entity type to use [optimistic concurrency](xref:core/modeling/concurrency) call <xref:Microsoft.EntityFrameworkCore.CosmosEntityTypeBuilderExtensions.UseETagConcurrency%2A>. This call will create an `_etag` property in [shadow state](xref:core/modeling/shadow-properties) and set it as the concurrency token.
+To configure an entity type to use [optimistic concurrency](xref:core/saving/concurrency) call <xref:Microsoft.EntityFrameworkCore.CosmosEntityTypeBuilderExtensions.UseETagConcurrency%2A>. This call will create an `_etag` property in [shadow state](xref:core/modeling/shadow-properties) and set it as the concurrency token.
 
 [!code-csharp[Main](../../../../samples/core/Cosmos/ModelBuilding/OrderContext.cs?name=ETag)]