Correct GitHub issue number (#3901)

dotnet · Jun 19, 2022 · b251b79 · b251b79
1 parent ab5a629
commit b251b79
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/entity-framework/core/modeling/value-conversions.md b/entity-framework/core/modeling/value-conversions.md
@@ -794,7 +794,7 @@ There are a few known current limitations of the value conversion system:
 * As noted above, `null` cannot be converted. Please vote (👍) for [GitHub issue #13850](https://github.com/dotnet/efcore/issues/13850) if this is something you need.
 * There is currently no way to spread a conversion of one property to multiple columns or vice-versa. Please vote (👍) for [GitHub issue #13947](https://github.com/dotnet/efcore/issues/13947) if this is something you need.
 * Value generation is not supported for most keys mapped through value converters. Please vote (👍) for [GitHub issue #11597](https://github.com/dotnet/efcore/issues/11597) if this is something you need.
-* Value conversions cannot reference the current DbContext instance. Please vote (👍) for [GitHub issue #11597](https://github.com/dotnet/efcore/issues/12205) if this is something you need.
+* Value conversions cannot reference the current DbContext instance. Please vote (👍) for [GitHub issue #12205](https://github.com/dotnet/efcore/issues/12205) if this is something you need.
 * Parameters using value-converted types cannot currently be used in raw SQL APIs. Please vote (👍) for [GitHub issue #27534](https://github.com/dotnet/efcore/issues/27354) if this is something you need.
 
 Removal of these limitations is being considered for future releases.