From 2cbdde9d4a2933f203ba614e87316f5bffb62070 Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Mon, 22 Jun 2026 12:06:13 -0700 Subject: [PATCH] fix broken links --- xml/System.Text/Rune.xml | 2 +- xml/System/Exception.xml | 3 +-- xml/System/IDisposable.xml | 2 +- xml/System/String.xml | 7 ++----- 4 files changed, 5 insertions(+), 9 deletions(-) diff --git a/xml/System.Text/Rune.xml b/xml/System.Text/Rune.xml index 01e262d58dc..2b9f5ebe6ab 100644 --- a/xml/System.Text/Rune.xml +++ b/xml/System.Text/Rune.xml @@ -256,7 +256,7 @@ The and without validating its arguments beforehand. +The recommended way to re-throw an exception is to simply use the [throw](/dotnet/csharp/language-reference/keywords/throw) statement in C#, the [reraise](/dotnet/fsharp/language-reference/exception-handling/the-raise-function#reraising-an-exception) function in F#, and the [Throw](/dotnet/visual-basic/language-reference/statements/throw-statement) statement in Visual Basic without including an expression. This ensures that all call stack information is preserved when the exception is propagated to the caller. The following example illustrates this. A string extension method, `FindOccurrences`, wraps one or more calls to without validating its arguments beforehand. :::code language="csharp" source="~/snippets/csharp/System/Exception/Overview/rethrow1.cs" id="Snippet6"::: :::code language="fsharp" source="~/snippets/fsharp/System/Exception/Overview/rethrow1.fs" id="Snippet6"::: diff --git a/xml/System/IDisposable.xml b/xml/System/IDisposable.xml index 29bfcf90493..7a3d3fcc8c8 100644 --- a/xml/System/IDisposable.xml +++ b/xml/System/IDisposable.xml @@ -92,7 +92,7 @@ For more information about the `try`/`finally` pattern, see [try-finally (C#)](/ ## Implement IDisposable -You should implement if your type uses unmanaged resources directly or if you wish to use disposable resources yourself. The consumers of your type can call your implementation to free resources when the instance is no longer needed. To handle cases in which they fail to call , you should either use a class derived from to wrap the unmanaged resources, or you should override the method for a reference type. In either case, you use the method to perform whatever cleanup is necessary after using the unmanaged resources, such as freeing, releasing, or resetting the unmanaged resources. For more information about implementing , see [the Dispose(bool) method overload](/dotnet/standard/garbage-collection/implementing-dispose.md#the-disposebool-method-overload). +You should implement if your type uses unmanaged resources directly or if you wish to use disposable resources yourself. The consumers of your type can call your implementation to free resources when the instance is no longer needed. To handle cases in which they fail to call , you should either use a class derived from to wrap the unmanaged resources, or you should override the method for a reference type. In either case, you use the method to perform whatever cleanup is necessary after using the unmanaged resources, such as freeing, releasing, or resetting the unmanaged resources. For more information about implementing , see [the Dispose(bool) method overload](/dotnet/standard/garbage-collection/implementing-dispose#the-disposebool-method-overload). > [!IMPORTANT] > If you're defining a base class that uses unmanaged resources and that either has, or is likely to have, subclasses that should be disposed, you should implement the method and provide a second overload of `Dispose`, as discussed in the next section. diff --git a/xml/System/String.xml b/xml/System/String.xml index 051f6bdb669..0ec1fe11b25 100644 --- a/xml/System/String.xml +++ b/xml/System/String.xml @@ -5771,7 +5771,7 @@ A format item has this syntax: {index[,width][:formatString]} ``` -Brackets denote optional elements. The opening and closing braces are required. (To include a literal opening or closing brace in the format string, see the [Escaping Braces](/dotnet/standard/base-types/composite-formatting.md#escaping-braces) section in the [Composite Formatting](/dotnet/standard/base-types/composite-formatting) article.) +Brackets denote optional elements. The opening and closing braces are required. (To include a literal opening or closing brace in the format string, see the [Escaping Braces](/dotnet/standard/base-types/composite-formatting#escaping-braces) section in the [Composite Formatting](/dotnet/standard/base-types/composite-formatting) article.) For example, a format item to format a currency value might appear like this: @@ -5815,16 +5815,13 @@ The following example uses the `width` and `formatString` arguments to produce f Format items are processed sequentially from the beginning of the string. Each format item has an index that corresponds to an object in the method's argument list. The method retrieves the argument and derives its string representation as follows: - If the argument is `null`, the method inserts into the result string. You don't have to be concerned with handling a for null arguments. - - If you call the overload and the `provider` object's implementation returns a non-null implementation, the argument is passed to its method. If the format item includes a `formatString` argument, it is passed as the first argument to the method. If the implementation is available and produces a non-null string, that string is returned as the string representation of the argument; otherwise, the next step executes. - - If the argument implements the interface, its implementation is called. - - The argument's parameterless `ToString` method, which either overrides or inherits from a base class implementation, is called. For an example that intercepts calls to the method and allows you to see what information the method passes to a formatting method for each format item in a composite format string, see [Example: An intercept provider and Roman numeral formatter](#example-an-intercept-provider-and-roman-numeral-formatter). -For more information, see [Processing order](/dotnet/standard/base-types/composite-formatting.md#processing-order). +For more information, see [Processing order](/dotnet/standard/base-types/composite-formatting#processing-order). ## Format items that have the same index