fixed view

Author: JustPies

docs/c-runtime-library/crt-debugging-techniques.md

@@ -169,5 +169,5 @@ If the hook handles the message in question completely, so that no further repor
 
 ## See also
 
-- [Debugging Native Code](/visualstudio/debugger/debugging-native-code?view=vs-2022)
-- [Debugger Security](/visualstudio/debugger/debugger-security?view=vs-2022)
+- [Debugging Native Code](/visualstudio/debugger/debugging-native-code)
+- [Debugger Security](/visualstudio/debugger/debugger-security)

docs/c-runtime-library/find-memory-leaks-using-the-crt-library.md

@@ -216,7 +216,7 @@ You can use the allocation number to set a breakpoint on the memory allocation.
 
 After you set a breakpoint on a memory-allocation number, continue to debug. Make sure to run under the same conditions, so the memory-allocation number doesn't change. When your program breaks at the specified memory allocation, use the **Call Stack** window and other debugger windows to determine the conditions under which the memory was allocated. Then, you can continue execution to observe what happens to the object and determine why it isn't correctly deallocated.
 
-Setting a data breakpoint on the object might also be helpful. For more information, see [Using breakpoints](/visualstudio/debugger/using-breakpoints?view=vs-2022).
+Setting a data breakpoint on the object might also be helpful. For more information, see [Using breakpoints](/visualstudio/debugger/using-breakpoints).
 
 You can also set memory-allocation breakpoints in code. You can set:
 
@@ -281,5 +281,5 @@ One technique for finding memory leaks begins by placing `_CrtMemCheckpoint` cal
 ## See also
 
 - [CRT debug heap details](./crt-debug-heap-details.md)
-- [Debugger security](/visualstudio/debugger/debugger-security?view=vs-2022)
-- [Debugging native code](/visualstudio/debugger/debugging-native-code?view=vs-2022)
+- [Debugger security](/visualstudio/debugger/debugger-security)
+- [Debugging native code](/visualstudio/debugger/debugging-native-code)

docs/data/odbc/odbc-and-mfc.md

@@ -8,7 +8,7 @@ ms.assetid: 98f02fd7-1235-437b-89a9-edfd0fc797f7
 # ODBC and MFC
 
 > [!NOTE]
-> To use the MFC database classes, you must have the appropriate ODBC driver for your data source. The lastest Microsoft ODBC driver for SQL Server is [Microsoft ODBC Driver 18 for SQL Server](/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16). Most database vendors provide an ODBC driver for Windows.
+> To use the MFC database classes, you must have the appropriate ODBC driver for your data source. The lastest Microsoft ODBC driver for SQL Server is [Microsoft ODBC Driver 18 for SQL Server](/sql/connect/odbc/download-odbc-driver-for-sql-server. Most database vendors provide an ODBC driver for Windows.
 
 This topic introduces the main concepts of the Microsoft Foundation Classes (MFC) library's ODBC-based database classes and provides an overview of how the classes work together. For more information about ODBC and MFC, see the following topics: