20). Add topic files 51 to 54

.openpublishing.redirection.json

@@ -1513,6 +1513,26 @@
       "redirect_url": "/dotnet/standard/linq/query-xdocument-vs-query-xelement",
       "redirect_document_id": true
     },
+    {
+      "source_path": "docs/csharp/programming-guide/concepts/linq/how-to-filter-on-an-optional-element.md",
+      "redirect_url": "/dotnet/standard/linq/filter-optional-element",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/csharp/programming-guide/concepts/linq/how-to-find-all-nodes-in-a-namespace.md",
+      "redirect_url": "/dotnet/standard/linq/find-all-nodes-namespace",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/csharp/programming-guide/concepts/linq/how-to-sort-elements.md",
+      "redirect_url": "/dotnet/standard/linq/sort-elements",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/csharp/programming-guide/concepts/linq/how-to-write-queries-with-complex-filtering.md",
+      "redirect_url": "/dotnet/standard/linq/write-queries-complex-filtering",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/csharp/programming-guide/concepts/threading/how-to-use-a-thread-pool.md",
       "redirect_url": "/dotnet/api/system.threading.threadpool.queueuserworkitem"
@@ -4784,6 +4804,26 @@
       "redirect_url": "/dotnet/standard/linq/query-xdocument-vs-query-xelement",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/visual-basic/programming-guide/concepts/linq/how-to-filter-on-an-optional-element.md",
+      "redirect_url": "/dotnet/standard/linq/filter-optional-element",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/visual-basic/programming-guide/concepts/linq/how-to-find-all-nodes-in-a-namespace.md",
+      "redirect_url": "/dotnet/standard/linq/find-all-nodes-namespace",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/visual-basic/programming-guide/concepts/linq/how-to-sort-elements.md",
+      "redirect_url": "/dotnet/standard/linq/sort-elements",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/visual-basic/programming-guide/concepts/linq/how-to-write-queries-with-complex-filtering.md",
+      "redirect_url": "/dotnet/standard/linq/write-queries-complex-filtering",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/visual-basic/programming-guide/concepts/threading/how-to-use-a-thread-pool.md",
       "redirect_url": "/dotnet/api/system.threading.threadpool.queueuserworkitem"

docs/standard/linq/catch-parsing-errors.md

@@ -12,7 +12,7 @@ ms.assetid: bfb612d4-5605-48ef-8c93-915cf9d5dcfb
 
 This article shows how to detect badly formed or invalid XML in C# or Visual Basic.
 
-LINQ to XML is implemented using <xref:System.Xml.XmlReader>. If badly formed or invalid XML is passed to LINQ to XML, the underlying <xref:System.Xml.XmlReader> class will throw an exception. The various methods that parse XML, such as <xref:System.Xml.Linq.XElement.Parse%2A?displayProperty=nameWithType>, do not catch the exception; the exception can then be caught by your application.
+LINQ to XML is implemented using <xref:System.Xml.XmlReader>. If badly formed or invalid XML is passed to LINQ to XML, the underlying <xref:System.Xml.XmlReader> class will throw an exception. The various methods that parse XML, such as <xref:System.Xml.Linq.XElement.Parse%2A?displayProperty=nameWithType>, don't catch the exception; the exception can then be caught by your application.
 
 ## Example: Parse invalid XML