diff --git a/_content/survey2020-results.article b/_content/survey2020-results.article
index 2c1861d..617900d 100644
--- a/_content/survey2020-results.article
+++ b/_content/survey2020-results.article
@@ -6,15 +6,15 @@
 Alice Merrick
 amerrick@google.com
 
-## Thank you for the amazing response!
+## Thank you for the amazing response! {#thanks}
 
 In 2020, we had another great turnout with 9,648 responses, about [as many as 2019](https://blog.golang.org/survey2019-results). Thank you for putting in the time to provide the community with these insights on your experiences using Go!
 
-## New modular survey design
+## New modular survey design {#new}
 
-You may notice some questions have smaller sample sizes ("n=") than others. That's because some questions were shown to everyone while others were only shown to a random subset of respondents. 
+You may notice some questions have smaller sample sizes ("n=") than others. That's because some questions were shown to everyone while others were only shown to a random subset of respondents.
 
-## Highlights
+## Highlights {#highlights}
 
 - Go usage is expanding in the workplace and enterprise with 76% of respondents using [Go at work](#TOC_4.1) and 66% saying [Go is critical to their company's success](#TOC_6.1).
 - [Overall satisfaction](#TOC_6.) is high with 92% of respondents being satisfied using Go.
@@ -22,11 +22,11 @@
 - Respondents reported [upgrading promptly to the latest Go version](#TOC_7.), with 76% in the first 5 months.
 - [Respondents using pkg.go.dev are more successful (91%)](#TOC_12.) at finding Go packages than non-users (82%).
 - Go [modules adoption is nearly universal](#TOC_8.) with 77% satisfaction, but respondents also highlight a need for improved docs.
-- Go continues to be heavily used for [APIs, CLIs, Web, DevOps & Data Processing](#TOC_7.). 
-- [Underrepresented groups](#TOC_12.1) tend to feel less welcome in the community. 
+- Go continues to be heavily used for [APIs, CLIs, Web, DevOps & Data Processing](#TOC_7.).
+- [Underrepresented groups](#TOC_12.1) tend to feel less welcome in the community.
 
 
-## Who did we hear from?
+## Who did we hear from? {#who}
 
 Demographic questions help us distinguish which year-over-year differences may result from changes in who responded to the survey versus changes in sentiment or behavior. Because our demographics are similar to last year, we can be reasonably confident that other year-over-year changes aren't primarily due to demographic shifts.
 
@@ -37,7 +37,7 @@
 <img src="survey2020/devex_yoy.svg" alt="Bar chart of years of professional experience for 2019 to 2020 with the majority having 3 to 10 years of experience" width="700"/>
 <img src="survey2020/industry_yoy.svg" alt="Bar chart of organization industries for 2019 to 2020 with the majority in Technology" width="700"/>
 
-Almost half (48%) of respondents have been using Go for less than two years. In 2020, we had fewer responses from those using Go for less than a year. 
+Almost half (48%) of respondents have been using Go for less than two years. In 2020, we had fewer responses from those using Go for less than a year.
 
 <img src="survey2020/goex_yoy.svg" alt="Bar chart of years of experience using Go" width="700"/>
 
@@ -56,7 +56,7 @@
 
 <img src="survey2020/foss_yoy.svg" alt="How often respondents contribute to open source projects written in Go from 2017 to 2020 where results remain about the same each year and only 7% contribute daily" width="700"/>
 
-## Developer tools and practices
+## Developer tools and practices {#devtools}
 
 As in prior years, the vast majority of survey respondents reported working
 with Go on Linux (63%) and macOS (55%) systems. The proportion of respondents who primarily develop on Linux appears to be slightly trending down over time.
@@ -75,14 +75,14 @@
 
 <img src="survey2020/refactor_time.svg" alt="Bar chart of time spent refactoring" width="700"/>
 
-Last year we asked about specific developer techniques and found that almost 90% of respondents were using text logging for debugging, so this year we added a follow-up question to find out why. Results show that 43% use it because it allows them to use the same debugging strategy across different languages, and 42% prefer to use text logging over other debugging techniques. 
+Last year we asked about specific developer techniques and found that almost 90% of respondents were using text logging for debugging, so this year we added a follow-up question to find out why. Results show that 43% use it because it allows them to use the same debugging strategy across different languages, and 42% prefer to use text logging over other debugging techniques.
 However, 27% don't know how to get started with Go's debugging tools and 24% have never tried using Go's debugging tools, so there's an opportunity to improve the debugger tooling in terms of discoverability, usability and documentation.
 Additionally, because a quarter of respondents have never tried using debugging tools, pain points may be underreported.
 
 <img src="survey2020/why_printf.svg" alt="" width="700"/>
 
 
-## Sentiments towards Go
+## Sentiments towards Go {#sentiments}
 
 For the first time, this year we asked about overall satisfaction. 92% of respondents said they were very or somewhat satisfied using Go during the past year.
 
@@ -122,19 +122,19 @@
 
 <img src="survey2020/attitudes_community_yoy.svg" alt="Bar chart showing agreement with statements I feel welcome in the Go community, I am confident in the Go leadership, I feel welcome to contribute, The Go project leadership understands my needs, and The process of contributing to the Go project is clear to me" width="700"/>
 
-We asked an open text question on what we could do to make the Go community more welcoming and the most common recommendations (21%) were related to different forms of or improvements/additions to learning resources and documentation. 
+We asked an open text question on what we could do to make the Go community more welcoming and the most common recommendations (21%) were related to different forms of or improvements/additions to learning resources and documentation.
 
 <img src="survey2020/more_welcoming.svg" alt="Bar chart of recommendations for improving the welcomeness of the Go community" width="700"/>
 
 
-## Working with Go
+## Working with Go {#uses}
 
 Building API/RPC services (74%) and CLIs (65%) remain the most common uses of Go. We don't see any significant changes from last year, when we introduced randomization into the ordering of options. (Prior to 2019, options towards the beginning of the list were disproportionately selected.)
-We also broke this out by organization size and found that respondents use Go similarly at large enterprises or smaller organizations, although large orgs are a little less likely to use Go for web services returning HTML. 
+We also broke this out by organization size and found that respondents use Go similarly at large enterprises or smaller organizations, although large orgs are a little less likely to use Go for web services returning HTML.
 
 <img src="survey2020/app_yoy.svg" alt="Bar chart of Go use cases from 2019 to 2020 including API or RPC services, CLIs, frameworks, web services, automation, agents and daemons, data processing, GUIs, games and mobile apps" width="700"/>
 
-This year we now have a better understanding of which kinds of software respondents write in Go at home versus at work. Although web services returning HTML is the 4th most common use case, this is due to non-work related use. More respondents use Go for automation/scripts, agents and daemons, and data processing for work than web services returning HTML. 
+This year we now have a better understanding of which kinds of software respondents write in Go at home versus at work. Although web services returning HTML is the 4th most common use case, this is due to non-work related use. More respondents use Go for automation/scripts, agents and daemons, and data processing for work than web services returning HTML.
 A greater proportion of the least common uses (desktop/GUI apps, games, and mobile apps) are being written outside of work.
 
 <img src="survey2020/app_context.svg" alt="Stacked bar charts of proportion of use case is at work, outside of work, or both " width="700"/>
@@ -142,12 +142,12 @@
 Another new question asked how satisfied respondents were for each use case.
 CLIs had the highest satisfaction, with 85% of respondents saying they were very, moderately or slightly satisfied using Go for CLIs.
 Common uses for Go tended to have higher satisfaction scores, but satisfaction and popularity don’t perfectly correspond.
-For example, agents and daemons has 2nd highest proportion of satisfaction but it’s 6th in usage. 
+For example, agents and daemons has 2nd highest proportion of satisfaction but it’s 6th in usage.
 
 <img src="survey2020/app_sat_bin.svg" alt="Bar chart of satisfaction with each use case" width="700"/>
 
 Additional follow-up questions explored different use cases, for example, which platforms respondents target with their CLIs.
-It's not surprising to see Linux (93%) and macOS (59%) highly represented, given the high developer use of Linux and macOS and high Linux cloud usage), but even Windows is targeted by almost a third of CLI developers. 
+It's not surprising to see Linux (93%) and macOS (59%) highly represented, given the high developer use of Linux and macOS and high Linux cloud usage), but even Windows is targeted by almost a third of CLI developers.
 
 <img src="survey2020/cli_platforms.svg" alt="Bar chart of platforms being targeted for CLIs" width="700"/>
 
@@ -169,13 +169,14 @@
 
 <img src="survey2020/update_time.svg" alt="Bar chart of how soon respondents begin evaluating a new Go release" width="700"/>
 
-## Modules
-This year we found near-universal adoption for Go modules, and a significant increase in the proportion of respondents who only use modules for package management. 96% of respondents said they were using modules for package management, up from 89% last year. 87% of respondents said they were using _only_ modules for package management, up from 71% last year. 
+## Modules {#modules}
+
+This year we found near-universal adoption for Go modules, and a significant increase in the proportion of respondents who only use modules for package management. 96% of respondents said they were using modules for package management, up from 89% last year. 87% of respondents said they were using _only_ modules for package management, up from 71% last year.
 Meanwhile, the use of other package management tools has decreased.
 
 <img src="survey2020/modules_adoption_yoy.svg" alt="Bar chart of methods used for Go package management" width="700"/>
 
-Satisfaction with modules also increased from last year. 77% of respondents said they were very, moderately or slightly satisfied with modules, compared to 68% in 2019. 
+Satisfaction with modules also increased from last year. 77% of respondents said they were very, moderately or slightly satisfied with modules, compared to 68% in 2019.
 
 <img src="survey2020/modules_sat_yoy.svg" alt="Stacked bar chart of satisfaction with using modules on a 7 point scale from very dissatisfied to very satisfied" width="700"/>
 
@@ -188,7 +189,7 @@
 
 <img src="survey2020/doc_helpfulness.svg" alt="Stacked bar charts on helpfulness of specific areas of documentation including using modules, CLI tool development, error handling, web service development, data access, concurrency and file input/output, rated on a 5 point scale from not at all to very helpful" width="700"/>
 
-## Go in the clouds
+## Go in the clouds {#cloud}
 
 Go was designed with modern distributed computing in mind,
 and we want to continue to improve the developer experience of building
@@ -197,7 +198,7 @@
 - The three largest global cloud providers (Amazon Web Services,
 Google Cloud Platform, and Microsoft Azure) continue to increase
 in usage among survey respondents,
-while most other providers are used by a smaller proportion of respondents each year. 
+while most other providers are used by a smaller proportion of respondents each year.
 Azure in particular had a significant increase from 7% to 12%.
 - On-prem deployments to self-owned or company-owned servers continue to
 decrease as the most common deployment targets.
@@ -218,14 +219,14 @@
 
 <img src="survey2020/cloud_csat.svg" alt="Stacked bar chart of satisfaction with using Go with AWS, GCP and Azure" width="700"/>
 
-## Pain points
+## Pain points {#pain}
 
 The top reasons respondents say they are unable to use Go more remain working
 on a project in another language (54%),
 working on a team that prefers to use another language (34%),
 and the lack of a critical feature in Go itself (26%).
 
-This year we introduced a new option, “I already use Go everywhere I would like to,” so that respondents could opt out of making selections that don't prevent them from using Go. This significantly lowered the rate of selection of all other options, but did not change their relative ordering. 
+This year we introduced a new option, “I already use Go everywhere I would like to,” so that respondents could opt out of making selections that don't prevent them from using Go. This significantly lowered the rate of selection of all other options, but did not change their relative ordering.
 We also introduced an option for “Go lacks critical frameworks”.
 
 If we look at only the respondents who selected reasons for not using Go, we can get a better idea of year-over-year trends. Working on an existing project in another language and project/team/lead preference for another language are decreasing over time.
@@ -234,7 +235,7 @@
 
 Among the 26% of respondents who said Go lacks language features they need,
 88% selected generics as a critical missing feature.
-Other critical missing features were better error handling (58%), null safety (44%), functional programming features(42%) and 
+Other critical missing features were better error handling (58%), null safety (44%), functional programming features(42%) and
 a stronger / expanded type system (41%).
 
 To be clear, these numbers are from the subset of respondents who said they
@@ -247,7 +248,7 @@
 
 <img src="survey2020/biggest_challenge.svg" alt="Bar chart of biggest challenges respondents face when using Go" width="700"/>
 
-## The Go community
+## The Go community {#community}
 
 This year we asked respondents for their top 5 resources for answering their Go-related questions. Last year we only asked for top 3, so the results aren't directly comparable, however, StackOverflow remains the most popular resource at 65%.
 Reading source code (57%) remains another popular resource while reliance on godoc.org (39%) has significantly decreased. The package discovery site pkg.go.dev is new to the list this year and was a top resource for 32% of respondents. Respondents who use pkg.go.dev are more likely to agree they are able to quickly find Go packages / libraries they need: 91% for pkg.go.dev users vs. 82% for everyone else.
@@ -260,9 +261,9 @@
 <img src="survey2020/events.svg" alt="Bar chart of respondents participation in online channels and events" width="700"/>
 
 <p id="TOC_12.1">We found 12% of respondents identify with a traditionally underrepresented group (e.g.,
-ethnicity, gender identity, et al.), the same as 2019, and 2% identify as women, fewer than in 2019 (3%). 
-Respondents who identified with underrepresented groups showed higher rates of disagreement with the statement 
-"I feel welcome in the Go community" (10% vs. 4%) than those who do not identify with an underrepresented group. These questions allow us to measure diversity in the community and highlight opportunities for outreach and growth.</p>  
+ethnicity, gender identity, et al.), the same as 2019, and 2% identify as women, fewer than in 2019 (3%).
+Respondents who identified with underrepresented groups showed higher rates of disagreement with the statement
+"I feel welcome in the Go community" (10% vs. 4%) than those who do not identify with an underrepresented group. These questions allow us to measure diversity in the community and highlight opportunities for outreach and growth.</p>
 
 <img src="survey2020/underrep.svg" alt="Bar chart of underrepresented groups" width="700"/>
 <img src="survey2020/underrep_groups_women.svg" alt="Bar chart of those who identify as women" width="700"/>
@@ -275,7 +276,7 @@
 The Go team values diversity and inclusion, not simply as the right thing to do, but because diverse voices can illuminate our blindspots and ultimately benefit all users. The way we ask about sensitive information, including gender and traditionally underrepresented groups, has changed according to data privacy regulations and we hope to make these questions, particularly around gender diversity, more inclusive in the future.
 
 
-## Conclusion
+## Conclusion {#conclusion}
 
 Thank you for joining us in reviewing the results of our 2020 developer survey!
 Understanding developers’ experiences and challenges helps us measure our progress and directs the future of Go.