Skip to content

Commit cc45f09

Browse files
committed
Change straight quotes to curly quotes
1 parent 76ceb11 commit cc45f09

File tree

22 files changed

+76
-76
lines changed

22 files changed

+76
-76
lines changed

templates/404.hbs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
<div class="row">
55
<div class="eight columns">
66
<h1>404</h1>
7-
<h2 class="subtitle">Whoops, this page doesn't exist :-(</h2>
7+
<h2 class="subtitle">Whoops, this page doesnt exist :-(</h2>
88
</div>
99
<div class="four columns">
1010
<img id="ferris-error" src="/static/images/ferris-error.png" alt="404 not found image">

templates/community/index.hbs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515

1616
</p>
1717
<p>
18-
We'd like to hear from you! Not sure where or who to ask a question? Want to get involved but aren't sure how?
18+
Wed like to hear from you! Not sure where or who to ask a question? Want to get involved but arent sure how?
1919
The community team is eager to connect you with someone who can help!
2020
</p>
2121
<a href="mailto:[email protected]" class="center mw8 button button-secondary">email [email protected]</a>
@@ -112,7 +112,7 @@
112112
<div>
113113
<h3>Run your own event</h3>
114114
<p>
115-
As Rust grows, we're excited to help folks start their own local events.
115+
As Rust grows, were excited to help folks start their own local events.
116116
From hack and learns, to meetups, to conferences, the Rust Events Team is
117117
ready to help support you.
118118
</p>
@@ -171,7 +171,7 @@
171171
<section id="rustreach" class="red">
172172
<div class="w-100 mw-none ph3 mw8-m mw9-l center">
173173
<header>
174-
<h2>Increasing Rust's Reach</h2>
174+
<h2>Increasing Rusts Reach</h2>
175175
<div class="highlight"></div>
176176
</header>
177177
<div class="w-100 flex flex-column flex-row-l">
@@ -180,7 +180,7 @@
180180
</div>
181181
<div class="mw-67-l mh3-l">
182182
<p>
183-
Increasing Rust's Reach is a program matches Rust team members from all parts of the project with individuals who are underrepresented in Rust's community and the tech industry for a partnership of three (3) months, from mid-May to mid-August. Each partnership agrees to a commitment of 3–5 hours per week working on a Rust Project.
183+
Increasing Rusts Reach is a program matches Rust team members from all parts of the project with individuals who are underrepresented in Rusts community and the tech industry for a partnership of three (3) months, from mid-May to mid-August. Each partnership agrees to a commitment of 3–5 hours per week working on a Rust Project.
184184
</p>
185185
<a href="http://reach.rust-lang.org/" target="_blank" rel="noopener"
186186
class="button button-secondary">Visit Website</a>

templates/governance/index.hbs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
<div class="mw8 flex flex-column justify-between pt0 bp2 pv3-ns ph3-l">
1818
<p>Each major decision in Rust starts as a Request for Comments (RFC).
1919
Everyone is invited to discuss the proposal, to work toward a shared understanding of the tradeoffs.
20-
Though sometimes arduous, this community deliberation is Rust's secret sauce for quality.
20+
Though sometimes arduous, this community deliberation is Rusts secret sauce for quality.
2121
</p>
2222
<a href="https://github.com/rust-lang/rfcs" target="_blank" rel="noopener" class="button button-secondary">Learn
2323
more</a>
@@ -71,7 +71,7 @@
7171
<div class="highlight"></div>
7272
</header>
7373
<p>The Rust project belongs to its community of stakeholders, not to any one company or organization.
74-
It's built by a worldwide group of volunteers, students, and paid contributors.
74+
Its built by a worldwide group of volunteers, students, and paid contributors.
7575
Organizations that benefit from Rust give back by allocating employee time to Rust contribution
7676
or by sponsoring community efforts.
7777
There are people working part- and full-time on Rust at a half dozen companies, big and small.
@@ -86,7 +86,7 @@
8686
<h2>Community standards</h2>
8787
<div class="highlight"></div>
8888
</header>
89-
<p>Rust <i>is</i> its community, and so it's vital that its culture reflect the project's values:
89+
<p>Rust <i>is</i> its community, and so its vital that its culture reflect the projects values:
9090
inclusivity, empowerment, kindness, and careful deliberation. We have a Code of Conduct and a Moderation Team to
9191
enforce it, but in official venues we strive to go beyond that and treat each other with the highest standards of
9292
empathy and respect.</p>

templates/learn/get-started.hbs

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
<a href="/tools/install" class="button button-secondary">Learn more about installation</a>
2222
<hr />
2323
<h3><code>cargo</code>: the Rust build tool and package manager</h3>
24-
<p>When you install <code>rustup</code> you'll also get the latest stable version of the Rust build tool and
24+
<p>When you install <code>rustup</code> youll also get the latest stable version of the Rust build tool and
2525
package manager, also known as <code>cargo</code>. <code>cargo</code> does lots of things:</p>
2626
<ul>
2727
<li>build your project with <code>cargo build</code></li>
@@ -50,7 +50,7 @@
5050
<h2>Generating a new project</h2>
5151
<div class="highlight"></div>
5252
</header>
53-
<p>Let's write a small application with our new Rust development environment. To start, we'll use <code>cargo</code> to
53+
<p>Lets write a small application with our new Rust development environment. To start, well use <code>cargo</code> to
5454
make a new project for us. In your terminal of choice run:</p>
5555
<p><code>cargo new hello-rust</code></p>
5656
<p>This will generate a new directory called <code>hello-rust</code> with the following files:</p>
@@ -60,9 +60,9 @@
6060
|- src
6161
|- main.rs</code></pre>
6262
</p>
63-
<p><code>Cargo.toml</code> is the manifest file for Rust. It's where you keep metadata for your project, as well as
63+
<p><code>Cargo.toml</code> is the manifest file for Rust. Its where you keep metadata for your project, as well as
6464
dependencies.</p>
65-
<p><code>src/main.rs</code> is where we'll write our application code.</p>
65+
<p><code>src/main.rs</code> is where well write our application code.</p>
6666
</div>
6767
</section>
6868

@@ -72,21 +72,21 @@
7272
<h2>Adding dependencies</h2>
7373
<div class="highlight"></div>
7474
</header>
75-
<p>Let's add a dependency to our application. You can find all sorts of libraries on <a href="https://crates.io"
75+
<p>Lets add a dependency to our application. You can find all sorts of libraries on <a href="https://crates.io"
7676
target="_blank" rel="noopener">crates.io</a>, the package registry for Rust. In Rust, we often refer to
7777
packages as "crates".</p>
78-
<p>In this project, we'll use a crate called <a href="https://crates.io/crates/ferris-says" target="_blank" rel="noopener"><code>ferris-says</code></a>.
79-
<p>In our <code>Cargo.toml</code> file we'll add this information (that we got from the crate page):</p>
78+
<p>In this project, well use a crate called <a href="https://crates.io/crates/ferris-says" target="_blank" rel="noopener"><code>ferris-says</code></a>.
79+
<p>In our <code>Cargo.toml</code> file well add this information (that we got from the crate page):</p>
8080
<p>
8181
<pre><code>[dependencies]
8282
ferris_says = "0.1"</code></pre>
8383
</p>
8484
<p>Now we can run:</p>
8585
<p><code>cargo build</code></p>
8686
<p>...and <code>cargo</code>will install our dependency for us.</p>
87-
<p>You'll see that running this command created a new file for us, <code>Cargo.lock</code>. This file is a log of
87+
<p>Youll see that running this command created a new file for us, <code>Cargo.lock</code>. This file is a log of
8888
the exact versions of the dependencies we are using locally.</p>
89-
<p>To use this dependency, we can open <code>main.rs</code>, remove everything that's in there (it's just another
89+
<p>To use this dependency, we can open <code>main.rs</code>, remove everything thats in there (its just another
9090
example), and add this line to it:</p>
9191
<p>
9292
<pre><code>use ferris_says::say;</code></pre>
@@ -102,7 +102,7 @@ ferris_says = "0.1"</code></pre>
102102
<h2>A small Rust application</h2>
103103
<div class="highlight"></div>
104104
</header>
105-
<p>Now let's write a small application with our new dependency. In our <code>main.rs</code>, add the following
105+
<p>Now lets write a small application with our new dependency. In our <code>main.rs</code>, add the following
106106
code:</p>
107107
<p>
108108
<pre><code>use ferris_says::say; // from the previous step
@@ -141,7 +141,7 @@ fn main() {
141141
<h2>Learn more!</h2>
142142
<div class="highlight"></div>
143143
</header>
144-
<p>You're a Rustacean now! Welcome! We're so glad to have you. When you're ready, hop over to our Learn page, where
144+
<p>Youre a Rustacean now! Welcome! Were so glad to have you. When youre ready, hop over to our Learn page, where
145145
you can find lots of books that will help you to continue on your Rust adventure.</p>
146146
<a href="/learn" class="button button-secondary">learn more!</a>
147147
</div>
@@ -150,13 +150,13 @@ fn main() {
150150
<section id="ferris" class="white">
151151
<div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
152152
<header>
153-
<h2>Who's this crab, Ferris?</h2>
153+
<h2>Whos this crab, Ferris?</h2>
154154
<div class="highlight"></div>
155155
</header>
156156
<p>Ferris (they/them) is the unofficial mascot of the Rust Community. Rust programmers call themselves
157157
"Rustaceans", which is a play on the word "crustacean", which is set of creatures, one of which is a crab!</p>
158158
<p>Ferris is a name playing off of the adjective, "ferrous", meaning of or pertaining to iron. Since Rust often
159-
forms on iron, it seemed like a fun origin for our mascot's name!</p>
159+
forms on iron, it seemed like a fun origin for our mascots name!</p>
160160
<p>You can find more images of Ferris on <a href="http://rustacean.net/" target="_blank" rel="noopener">http://rustacean.net/</a>.
161161
<img alt="a gif of ferris scurrying side to side" src=/static/images/ferris.gif />
162162
</div>

templates/learn/index.hbs

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,14 @@
1414
</header>
1515
<div class="flex flex-column flex-row-l justify-between">
1616
<section class="pt0">
17-
<p>Affectionately nicknamed "the book," The Rust Programming Language
17+
<p>Affectionately nicknamed the book, The Rust Programming Language
1818
will give you an overview of the language from first principles.
19-
You'll build a few projects along the way, and by the end, you'll have
19+
Youll build a few projects along the way, and by the end, youll have
2020
a solid grasp of the language.</p>
2121
<a class="button button-secondary" href="https://doc.rust-lang.org/book/">Read the Book!</a>
2222
</section>
2323
<section class="pl5-l pt4 pt0-l">
24-
<p>If reading multiple hundreds of pages about a language isn't your
24+
<p>If reading multiple hundreds of pages about a language isnt your
2525
style, then Rust By Example has you covered. While the book talks
2626
about code with a lot of words, RBE shows off a bunch of code, and
2727
keeps the talking to a minimum. It also includes exercises!</p>
@@ -58,7 +58,7 @@
5858
<a href="https://doc.rust-lang.org/cargo/index.html" target="_blank" rel="noopener"
5959
class="button button-secondary mw6-l w-100">Cargo Book</a>
6060
<p class="pl4-l">
61-
A book on Rust's package manager and build system.
61+
A book on Rusts package manager and build system.
6262
</p>
6363
</div>
6464

@@ -135,7 +135,7 @@
135135
<h2>Master Rust</h2>
136136
<div class="highlight"></div>
137137
</header>
138-
<p>Curious about the darkest corners of the language? Here's where you can get into the nitty-gritty:</p>
138+
<p>Curious about the darkest corners of the language? Heres where you can get into the nitty-gritty:</p>
139139
<section class="flex flex-column flex-row-l pv0-l">
140140
<div class="flex flex-row flex-column-l justify-between-l mw8 measure-wide-l pv4 pv5-m pv6-ns ph4-l">
141141
<div class="v-top tc-l">
@@ -159,11 +159,11 @@
159159
</div>
160160
<div class="v-top pl4 pl0-l pt0 pt3-l measure-wide-l flex-l flex-column-l flex-auto-l justify-between-l">
161161
<p> The Rustonomicon is your guidebook to the dark
162-
arts of unsafe Rust. It's also sometimes called "the 'nomicon."</p>
162+
arts of unsafe Rust. Its also sometimes called the nomicon.</p>
163163

164164
<a class="button button-secondary"
165165
href="https://doc.rust-lang.org/nomicon/index.html">
166-
Read the 'nomicon
166+
Read the nomicon
167167
</a>
168168
</div>
169169
</div>

templates/panels/domains.hbs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
Command Line
1919
</h3>
2020
<p class="flex-grow-1">
21-
Whip up a CLI tool quickly with Rust's robust ecosystem.
21+
Whip up a CLI tool quickly with Rusts robust ecosystem.
2222
Rust helps you maintain your app with confidence and distribute it with ease.
2323
</p>
2424
<a href="/what/cli" class="button button-secondary">Learn More</a>
@@ -36,7 +36,7 @@
3636
</h3>
3737
<p class="flex-grow-1">
3838
Use Rust to supercharge your JavaScript, one module at a time.
39-
Publish to npm, bundle with WebPack, and you're off to the races.
39+
Publish to npm, bundle with WebPack, and youre off to the races.
4040
</p>
4141
<a href="/what/wasm" class="button button-secondary">Learn More</a>
4242
</div>

templates/panels/language-values.hbs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
<section class="flex flex-column mw8 measure-wide-l pv3 pt4-ns ph3-l">
1919
<h3 class="f2 f1-l">Reliability</h3>
2020
<p class="f3 lh-copy">
21-
Rust's rich type system and ownership model guarantee memory-safety
21+
Rusts rich type system and ownership model guarantee memory-safety
2222
and thread-safety &mdash; and enable you to eliminate many other
2323
classes of bugs at compile-time.
2424
</p>

templates/policies/index.hbs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@
88

99
<section id="policies-index" class="purple">
1010
<div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
11-
<p>This page links to the comprehensive set of Rust's policies.</p>
11+
<p>This page links to the comprehensive set of Rusts policies.</p>
1212
<ul>
1313
<li><a href="/policies/code-of-conduct">Code of Conduct</a></li>
1414
<li><a href="/policies/licenses">Licenses</a></li>
1515
<li><a href="/policies/media-guide">Logo Policy and Media Guide</a></li>
1616
<li><a href="/policies/security">Security Disclosures</a></li>
1717
</ul>
18-
<p>Didn't find what you were looking for? Have a question? Please reach out!</p>
18+
<p>Didnt find what you were looking for? Have a question? Please reach out!</p>
1919
<a href="mailto:[email protected]" class="button button-secondary">Message the Core Team</a></p>
2020
</div>
2121
</section>

templates/policies/security.hbs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ time to responsibly disclose any issues you find.</p>
1919
<p>All security bugs in the Rust distribution should be reported by email to
2020
<a href="mailto:[email protected]">[email protected]</a>. This list
2121
is delivered to a small security team. Your email will be acknowledged within 24
22-
hours, and you'll receive a more detailed response to your email within 48
22+
hours, and youll receive a more detailed response to your email within 48
2323
hours indicating the next steps in handling your report. If you would like, you
2424
can encrypt your report using <a href="../rust-security-team-key.gpg.ascii">our public key</a>.
2525
This key is also <a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xEFB9860AE7520DAC" target="_blank" rel="noopener">On
26-
MIT's keyserver</a> and <a href="#key">reproduced below</a>.</p>
26+
MITs keyserver</a> and <a href="#key">reproduced below</a>.</p>
2727
<p>This email address receives a large amount of spam, so be sure to use a
2828
descriptive subject line to avoid having your report be missed. After the
2929
initial reply to your report, the security team will endeavor to keep you
@@ -43,7 +43,7 @@ can take (in order):</p>
4343
</ul>
4444
<p>Please note that the discussion forums and #rust-internals IRC channel are
4545
public areas. When escalating in these venues, please do not discuss your
46-
issue. Simply say that you're trying to get a hold of someone from the security
46+
issue. Simply say that youre trying to get a hold of someone from the security
4747
team.</p>
4848
<p><a class="button button-secondary" href="mailto:[email protected]">email [email protected]</a></p>
4949
</div>
@@ -63,7 +63,7 @@ team.</p>
6363
<li>Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement.</li>
6464
<li>On the embargo date, the <a href="https://groups.google.com/forum/#!forum/rustlang-security-announcements" target="_blank" rel="noopener"> Rust security mailing list</a> is sent a copy of the announcement. The changes are pushed to the public repository and new builds are deployed to rust-lang.org. Within 6 hours of the mailing list being notified, a copy of the advisory will be published on the Rust blog.</li>
6565
</ol>
66-
<p>This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however it's important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.</p>
66+
<p>This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however its important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.</p>
6767
</div>
6868
</section>
6969

0 commit comments

Comments
 (0)