Commit graph

6 commits

Author SHA1 Message Date
Bill Wagner
37efea9c83
markdown lint fixes for 8.0 proposals (#2318)
* markdown lint fixes for 8.0 proposals

Summary:

1. a few header formatting fixes
1. use `csharp` or `antlr` as the language identifier for code fences.
1. update links to relative links for articles published on docs.

* change the links to records.md to absolute links

When published on docs.microsoft.com, the links from these proposals will resolve to the source on dotnet/csharplang.

That's the desired behavior for records.md, because that is a proposal feature that has not been implemented.
2019-03-08 08:30:23 -05:00
Maira Wenzel
fb4d3f3ab3
fix broken links (#2320) 2019-03-07 17:38:27 -08:00
Bill Wagner
ab7ad82fd9
fix one bad link. (#2319) 2019-03-07 17:01:32 -05:00
Bill Wagner
8b7d2d5410 markdown lint changes to C# 7.0 proposals
These changes are to improve the experience for publishing these proposals.

One change should be carefully reviewed to ensure I didn't introduce any technical errors:
I translated the binary literals grammar into ANTLR to match all other specs and proposals.  See changes in proposals/csharp-7.0/binary-literals.md

Other changes are:
1. Use  consistent ATX headers, with one H1 per proposal.
1. use `csharp` as language identifier in code snippets
1. Use relative links to other markdown from the dotnet/csharplang repo. That way, when published on docs.microsoft.com, the links will resolve to the publsihed articles on the same site. (Links to content not being published are not modified.)
1. spelling / capitalization found by the lint tool.
2019-03-07 11:39:58 -05:00
Bill Wagner
fbd90c7a3b The spec for records is still in the parent directory
When this file was moved into the 7.0 proposals directory, the link to records should have been updated to the parent directory.
2019-03-04 20:41:06 -05:00
Neal Gafter
3708b698b5
Add draft spec for pattern-matching in C# 7. (#1778) 2018-08-13 11:23:35 -07:00