[x/blog] content: fix code block in Publishing Go Modules article

When indentation is used to create a code block immediately following
a list, Markdown syntax is ambiguous: it can be interpreted as another
text paragraph belonging to the last list entry, or as a standalone
code block.

The original behavior in CL 197637 made this unambiguously a code block
because the present format did not support lists. This changed when the
article was converted to use Markdown syntax in CL 222848.

Start using a fenced code block instead of indentation to resolve the
Markdown ambiguity and restore original behavior.

For golang/go#33955.

Change-Id: I9537bc72d7a32f90592942591b2688fb2f26c452
Reviewed-on: https://go-review.googlesource.com/c/blog/+/245017
Reviewed-by: Jean de Klerk <deklerk@google.com>
X-Blog-Commit: fb994f42d8394e948c3d58235828e9ed5f2f3077
1 file changed
tree: 29d3151b3b540b8c307d2c6c3ddcfc13c1dd4f16
  1. blog/
  2. AUTHORS
  3. CONTRIBUTING.md
  4. CONTRIBUTORS
  5. LICENSE
  6. PATENTS
  7. README.md
README.md

Go Website

This repository holds the Go Website server code and content.

Download/Install

The easiest way to install is to run go get -u golang.org/x/website. You can also manually git clone the repository to $GOPATH/src/golang.org/x/website.

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the time repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/website:” in the subject line, so it is easy to find.