Fix fixable warnings

conceptual/EFCore.PG/mapping/full-text-search.md

@@ -56,7 +56,7 @@ protected override void OnModelCreating(ModelBuilder modelBuilder)
 }
 ```
 
-#### [Older Versions](#tab/older)
+#### [Older Versions](#tab/pg-lt-12)
 
 First, modify the `OnModelCreating()` of your context class to add an index as follows:
 
@@ -119,7 +119,7 @@ modelBuilder.Entity<Blog>()
     .IsTsVectorExpressionIndex("english");
 ```
 
-#### [Older Versions](#tab/older)
+#### [Older Versions](#tab/lt-v5)
 
 Create a migration which will contain the index creation SQL (`dotnet ef migrations add ...`). At this point, open the generated migration with your editor and add the following:
 

conceptual/Npgsql/release-notes/7.0.md

@@ -82,7 +82,7 @@ using var command2 = new NpgsqlCommand("SELECT * FROM some_function($1, $2)", co
 };
 ```
 
-For more information on calling procedures and functions, see [this doc section](../basic-usage.html#stored-functions-and-procedures).
+For more information on calling procedures and functions, see [this doc section](../basic-usage.md#stored-functions-and-procedures).
 
 ### Managing type mappings at the connection level is no longer supported
 
@@ -117,7 +117,7 @@ For more context on this change, see the discussion in [#4377](https://github.co
 
 ### The logging API has been replaced by Microsoft.Extensions.Logging
 
-Npgsql previously had its own logging API, requiring special adapters to the standard logging libraries. This API has been removed in 7.0, and replaced with support for the standard Microsoft.Extensions.Logging package. See [Logging](../logging.md) for more information.
+Npgsql previously had its own logging API, requiring special adapters to the standard logging libraries. This API has been removed in 7.0, and replaced with support for the standard Microsoft.Extensions.Logging package. See [Logging](../diagnostics/logging.md) for more information.
 
 ### The obsoleted NpgsqlDateTime, NpgsqlDate and NpgsqlTimeSpan have been removed
 

conceptual/Npgsql/security.md

@@ -72,7 +72,7 @@ If the root CA of the server certificate isn't installed in your machine's CA st
 
 Note that Npgsql does not perform certificate revocation validation by default, since this is an optional extension not implemented by all providers and CAs. To turn on certificate revocation validation, specify `Check Certificate Revocation=true` on the connection string.
 
-Finally, if the above options aren't sufficient for your scenario, you can call <xref:Npgsql.NpgsqlDataSourceBuilder.UseUserCertificateValidationCallback?displayProperty=nameWithType> to provide your custom server certificate validation logic (this gets set on the underlying .NET [`SslStream`](https://docs.microsoft.com/dotnet/api/system.net.security.sslstream.-ctor#System_Net_Security_SslStream__ctor_System_IO_Stream_System_Boolean_System_Net_Security_RemoteCertificateValidationCallback_System_Net_Security_LocalCertificateSelectionCallback_)).
+Finally, if the above options aren't sufficient for your scenario, you can call <xref:Npgsql.NpgsqlDataSourceBuilder.UseUserCertificateValidationCallback(System.Net.Security.RemoteCertificateValidationCallback)?displayProperty=nameWithType> to provide your custom server certificate validation logic (this gets set on the underlying .NET [`SslStream`](https://docs.microsoft.com/dotnet/api/system.net.security.sslstream.-ctor#System_Net_Security_SslStream__ctor_System_IO_Stream_System_Boolean_System_Net_Security_RemoteCertificateValidationCallback_System_Net_Security_LocalCertificateSelectionCallback_)).
 
 ### Client certificates
 
@@ -84,7 +84,7 @@ PostgreSQL may be configured to require valid certificates from connecting clien
 
 To provide a password for a client certificate, set either the `SSL Password` (6.0 and higher) or `Client Certificate Key` (5.0 and lower) connection string parameter.
 
-Finally, you can call <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificate?displayProperty=nameWithType>, <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificates> or <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificatesUseClientCertificatesCallback> to programmatically provide a certificate, multiple certificates or a callback which returns certificates (this works like on the underlying .NET [`SslStream`](https://docs.microsoft.com/dotnet/api/system.net.security.sslstream.-ctor#System_Net_Security_SslStream__ctor_System_IO_Stream_System_Boolean_System_Net_Security_RemoteCertificateValidationCallback_System_Net_Security_LocalCertificateSelectionCallback_)).
+Finally, you can call <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificate(System.Security.Cryptography.X509Certificates.X509Certificate)?displayProperty=nameWithType>, <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificates(System.Security.Cryptography.X509Certificates.X509CertificateCollection)?displayProperty=nameWithType> or <xref:Npgsql.NpgsqlDataSourceBuilder.UseClientCertificatesCallback(System.Action{System.Security.Cryptography.X509Certificates.X509CertificateCollection})?displayProperty=nameWithType> to programmatically provide a certificate, multiple certificates or a callback which returns certificates (this works like on the underlying .NET [`SslStream`](https://docs.microsoft.com/dotnet/api/system.net.security.sslstream.-ctor#System_Net_Security_SslStream__ctor_System_IO_Stream_System_Boolean_System_Net_Security_RemoteCertificateValidationCallback_System_Net_Security_LocalCertificateSelectionCallback_)).
 
 > [!NOTE]
 > Npgsql supports .PFX and .PEM certificates starting with 6.0. Previously, only .PFX certificates were supported.

docfx.json

@@ -23,7 +23,7 @@
       ],
       "dest": "obj/api/EFCore.PG",
       "properties": {
-        "TargetFramework": "netstandard2.1"
+        "TargetFramework": "net6.0"
       }
     }
   ],