rust-lang · ashleygwilliams · Nov 29, 2018 · Nov 29, 2018
@@ -4,7 +4,7 @@
     <div class="row">
       <div class="eight columns">
         <h1>404</h1>
-        <h2 class="subtitle">Whoops, this page doesn't exist :-(</h2>
+        <h2 class="subtitle">Whoops, this page doesn’t exist :-(</h2>
       </div>
       <div class="four columns">
         <img id="ferris-error" src="/static/images/ferris-error.png" alt="404 not found image">

@@ -15,7 +15,7 @@
 
     </p>
     <p>
-      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?
+      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?
       The community team is eager to connect you with someone who can help!
     </p>
     <a href="mailto:[email protected]" class="center mw8 button button-secondary">email [email protected]</a>
@@ -112,7 +112,7 @@
         <div>
           <h3>Run your own event</h3>
           <p>
-            As Rust grows, we're excited to help folks start their own local events.
+            As Rust grows, we’re excited to help folks start their own local events.
             From hack and learns, to meetups, to conferences, the Rust Events Team is
             ready to help support you.
           </p>
@@ -171,7 +171,7 @@
 <section id="rustreach" class="red">
   <div class="w-100 mw-none ph3 mw8-m mw9-l center">
     <header>
-      <h2>Increasing Rust's Reach</h2>
+      <h2>Increasing Rust’s Reach</h2>
       <div class="highlight"></div>
     </header>
     <div class="w-100 flex flex-column flex-row-l">
@@ -180,7 +180,7 @@
       </div>
       <div class="mw-67-l mh3-l">
         <p>
-          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.
+          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.
         </p>
         <a href="http://reach.rust-lang.org/" target="_blank" rel="noopener"
            class="button button-secondary">Visit Website</a>

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

@@ -21,7 +21,7 @@
     <a href="/tools/install" class="button button-secondary">Learn more about installation</a>
     <hr />
     <h3><code>cargo</code>: the Rust build tool and package manager</h3>
-    <p>When you install <code>rustup</code> you'll also get the latest stable version of the Rust build tool and
+    <p>When you install <code>rustup</code> you’ll also get the latest stable version of the Rust build tool and
       package manager, also known as <code>cargo</code>. <code>cargo</code> does lots of things:</p>
       <ul>
         <li>build your project with <code>cargo build</code></li>
@@ -50,7 +50,7 @@
       <h2>Generating a new project</h2>
       <div class="highlight"></div>
     </header>
-    <p>Let's write a small application with our new Rust development environment. To start, we'll use <code>cargo</code> to
+    <p>Let’s write a small application with our new Rust development environment. To start, we’ll use <code>cargo</code> to
       make a new project for us. In your terminal of choice run:</p>
     <p><code>cargo new hello-rust</code></p>
     <p>This will generate a new directory called <code>hello-rust</code> with the following files:</p>
@@ -60,9 +60,9 @@
 |- src
   |- main.rs</code></pre>
     </p>
-    <p><code>Cargo.toml</code> is the manifest file for Rust. It's where you keep metadata for your project, as well as
+    <p><code>Cargo.toml</code> is the manifest file for Rust. It’s where you keep metadata for your project, as well as
       dependencies.</p>
-    <p><code>src/main.rs</code> is where we'll write our application code.</p>
+    <p><code>src/main.rs</code> is where we’ll write our application code.</p>
   </div>
 </section>
 
@@ -72,21 +72,21 @@
       <h2>Adding dependencies</h2>
       <div class="highlight"></div>
     </header>
-    <p>Let's add a dependency to our application. You can find all sorts of libraries on <a href="https://crates.io"
+    <p>Let’s add a dependency to our application. You can find all sorts of libraries on <a href="https://crates.io"
         target="_blank" rel="noopener">crates.io</a>, the package registry for Rust. In Rust, we often refer to
       packages as "crates".</p>
-    <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>.
-      <p>In our <code>Cargo.toml</code> file we'll add this information (that we got from the crate page):</p>
+    <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>.
+      <p>In our <code>Cargo.toml</code> file we’ll add this information (that we got from the crate page):</p>
       <p>
         <pre><code>[dependencies]
 ferris_says = "0.1"</code></pre>
       </p>
       <p>Now we can run:</p>
       <p><code>cargo build</code></p>
       <p>...and <code>cargo</code>will install our dependency for us.</p>
-      <p>You'll see that running this command created a new file for us, <code>Cargo.lock</code>. This file is a log of
+      <p>You’ll see that running this command created a new file for us, <code>Cargo.lock</code>. This file is a log of
         the exact versions of the dependencies we are using locally.</p>
-      <p>To use this dependency, we can open <code>main.rs</code>, remove everything that's in there (it's just another
+      <p>To use this dependency, we can open <code>main.rs</code>, remove everything that’s in there (it’s just another
         example), and add this line to it:</p>
       <p>
         <pre><code>use ferris_says::say;</code></pre>
@@ -102,7 +102,7 @@ ferris_says = "0.1"</code></pre>
       <h2>A small Rust application</h2>
       <div class="highlight"></div>
     </header>
-    <p>Now let's write a small application with our new dependency. In our <code>main.rs</code>, add the following
+    <p>Now let’s write a small application with our new dependency. In our <code>main.rs</code>, add the following
       code:</p>
     <p>
       <pre><code>use ferris_says::say; // from the previous step
@@ -141,7 +141,7 @@ fn main() {
       <h2>Learn more!</h2>
       <div class="highlight"></div>
     </header>
-    <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
+    <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
       you can find lots of books that will help you to continue on your Rust adventure.</p>
     <a href="/learn" class="button button-secondary">learn more!</a>
   </div>
@@ -150,13 +150,13 @@ fn main() {
 <section id="ferris" class="white">
   <div class="w-100 mw-none ph3 mw8-m mw9-l center f3">
     <header>
-      <h2>Who's this crab, Ferris?</h2>
+      <h2>Who’s this crab, Ferris?</h2>
       <div class="highlight"></div>
     </header>
     <p>Ferris (they/them) is the unofficial mascot of the Rust Community. Rust programmers call themselves
       "Rustaceans", which is a play on the word "crustacean", which is set of creatures, one of which is a crab!</p>
     <p>Ferris is a name playing off of the adjective, "ferrous", meaning of or pertaining to iron. Since Rust often
-      forms on iron, it seemed like a fun origin for our mascot's name!</p>
+      forms on iron, it seemed like a fun origin for our mascot’s name!</p>
     <p>You can find more images of Ferris on <a href="http://rustacean.net/" target="_blank" rel="noopener">http://rustacean.net/</a>.
       <img alt="a gif of ferris scurrying side to side" src=/static/images/ferris.gif />
   </div>

@@ -14,14 +14,14 @@
     </header>
     <div class="flex flex-column flex-row-l justify-between">
       <section class="pt0">
-        <p>Affectionately nicknamed "the book," The Rust Programming Language
+        <p>Affectionately nicknamed “the book,” The Rust Programming Language
           will give you an overview of the language from first principles.
-          You'll build a few projects along the way, and by the end, you'll have
+          You’ll build a few projects along the way, and by the end, you’ll have
         a solid grasp of the language.</p>
           <a class="button button-secondary" href="https://doc.rust-lang.org/book/">Read the Book!</a>
       </section>
       <section class="pl5-l pt4 pt0-l">
-        <p>If reading multiple hundreds of pages about a language isn't your
+        <p>If reading multiple hundreds of pages about a language isn’t your
           style, then Rust By Example has you covered. While the book talks
           about code with a lot of words, RBE shows off a bunch of code, and
           keeps the talking to a minimum. It also includes exercises!</p>
@@ -58,7 +58,7 @@
           <a href="https://doc.rust-lang.org/cargo/index.html" target="_blank" rel="noopener"
              class="button button-secondary mw6-l w-100">Cargo Book</a>
           <p class="pl4-l">
-            A book on Rust's package manager and build system.
+            A book on Rust’s package manager and build system.
           </p>
         </div>
 
@@ -135,7 +135,7 @@
       <h2>Master Rust</h2>
       <div class="highlight"></div>
     </header>
-    <p>Curious about the darkest corners of the language? Here's where you can get into the nitty-gritty:</p>
+    <p>Curious about the darkest corners of the language? Here’s where you can get into the nitty-gritty:</p>
     <section class="flex flex-column flex-row-l pv0-l">
       <div class="flex flex-row flex-column-l justify-between-l mw8 measure-wide-l pv4 pv5-m pv6-ns ph4-l">
         <div class="v-top tc-l">
@@ -159,11 +159,11 @@
         </div>
         <div class="v-top pl4 pl0-l pt0 pt3-l measure-wide-l flex-l flex-column-l flex-auto-l justify-between-l">
           <p> The Rustonomicon is your guidebook to the dark
-            arts of unsafe Rust. It's also sometimes called "the 'nomicon."</p>
+            arts of unsafe Rust. It’s also sometimes called “the ’nomicon.”</p>
 
           <a class="button button-secondary"
              href="https://doc.rust-lang.org/nomicon/index.html">
-            Read the 'nomicon
+            Read the ’nomicon
           </a>
         </div>
       </div>

@@ -18,7 +18,7 @@
             Command Line
           </h3>
           <p class="flex-grow-1">
-            Whip up a CLI tool quickly with Rust's robust ecosystem.
+            Whip up a CLI tool quickly with Rust’s robust ecosystem.
             Rust helps you maintain your app with confidence and distribute it with ease.
           </p>
           <a href="/what/cli" class="button button-secondary">Learn More</a>
@@ -36,7 +36,7 @@
           </h3>
           <p class="flex-grow-1">
           Use Rust to supercharge your JavaScript, one module at a time.
-          Publish to npm, bundle with WebPack, and you're off to the races.
+          Publish to npm, bundle with WebPack, and you’re off to the races.
           </p>
           <a href="/what/wasm" class="button button-secondary">Learn More</a>
         </div>

@@ -18,7 +18,7 @@
       <section class="flex flex-column mw8 measure-wide-l pv3 pt4-ns ph3-l">
         <h3 class="f2 f1-l">Reliability</h3>
         <p class="f3 lh-copy">
-          Rust's rich type system and ownership model guarantee memory-safety
+          Rust’s rich type system and ownership model guarantee memory-safety
           and thread-safety &mdash; and enable you to eliminate many other
           classes of bugs at compile-time.
         </p>

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

@@ -19,11 +19,11 @@ time to responsibly disclose any issues you find.</p>
     <p>All security bugs in the Rust distribution should be reported by email to
 <a href="mailto:[email protected]">[email protected]</a>. This list
 is delivered to a small security team. Your email will be acknowledged within 24
-hours, and you'll receive a more detailed response to your email within 48
+hours, and you’ll receive a more detailed response to your email within 48
 hours indicating the next steps in handling your report. If you would like, you
 can encrypt your report using <a href="../rust-security-team-key.gpg.ascii">our public key</a>.
 This key is also <a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xEFB9860AE7520DAC" target="_blank" rel="noopener">On
-MIT's keyserver</a> and <a href="#key">reproduced below</a>.</p>
+MIT’s keyserver</a> and <a href="#key">reproduced below</a>.</p>
     <p>This email address receives a large amount of spam, so be sure to use a
 descriptive subject line to avoid having your report be missed. After the
 initial reply to your report, the security team will endeavor to keep you
@@ -43,7 +43,7 @@ can take (in order):</p>
     </ul>
     <p>Please note that the discussion forums and #rust-internals IRC channel are
 public areas. When escalating in these venues, please do not discuss your
-issue. Simply say that you're trying to get a hold of someone from the security
+issue. Simply say that you’re trying to get a hold of someone from the security
 team.</p>
     <p><a class="button button-secondary" href="mailto:[email protected]">email [email protected]</a></p>
   </div>
@@ -63,7 +63,7 @@ team.</p>
       <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>
       <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>
     </ol>
-    <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>
+    <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>
   </div>
 </section>