Skip to content

Commit 456b6bb

Browse files
committed
respond to feedback
1 parent 9c1d28d commit 456b6bb

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

xml/System/String.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5564,7 +5564,7 @@ If you are new to the `String.Format` method, see <see href="/dotnet/fundamental
55645564

55655565
## Examples
55665566

5567-
Numerous examples that call the <xref:System.String.Format*> method are interspersed throughout this article. You can also download a complete set of `String.Format` examples, which are included a [.NET project for C#](/samples/dotnet/samples/string-format/).
5567+
Numerous examples that call the <xref:System.String.Format*> method are interspersed throughout this article. You can also download a complete set of `String.Format` examples, which are included in a [.NET project for C#](/samples/dotnet/samples/string-format/).
55685568

55695569
The following are some of the examples included in the article:
55705570

xml/System/Uri.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -163,7 +163,7 @@ Uri uri1 = new Uri("C:/test/path/file.txt") // Implicit file path.
163163
Uri uri2 = new Uri("file:///C:/test/path/file.txt") // Explicit file path.
164164
```
165165
166-
These implicit file paths are not compliant with the URI specification and should be avoided when possible. When using .NET on Unix-based systems, implicit file paths can be especially problematic, because an absolute implicit file path is *indistinguishable* from a relative path. When such ambiguity is present, <xref:System.Uri> default to interpreting the path as an absolute URI.
166+
These implicit file paths are not compliant with the URI specification and should be avoided when possible. When using .NET on Unix-based systems, implicit file paths can be especially problematic, because an absolute implicit file path is *indistinguishable* from a relative path. When such ambiguity is present, <xref:System.Uri> defaults to interpreting the path as an absolute URI.
167167
168168
## Security considerations
169169

0 commit comments

Comments
 (0)