From 721f7c0ab6d78c27c3dcc44eefed829b8c879c49 Mon Sep 17 00:00:00 2001
From: Julian Wollersberger
 <24991778+Julian-Wollersberger@users.noreply.github.com>
Date: Fri, 22 Nov 2019 22:49:48 +0100
Subject: [PATCH] Fixing Typos in 2019-11-12 Infrastructure Team Meeting

---
 posts/inside-rust/2019-11-18-infra-team-meeting.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/posts/inside-rust/2019-11-18-infra-team-meeting.md b/posts/inside-rust/2019-11-18-infra-team-meeting.md
index 6dc21ff16..74ce97f50 100644
--- a/posts/inside-rust/2019-11-18-infra-team-meeting.md
+++ b/posts/inside-rust/2019-11-18-infra-team-meeting.md
@@ -11,17 +11,17 @@ Attending: alexcrichton, kennytm, Mark-Simulacrum, pietroalbini, sgrif, shepmast
 
 ## Rust 1.14.0 Cargo artifacts on the rust-lang-ci S3 bucket
 
-Following on last meeting’s topics, pietroalbini investigate whether it would
+Following on last meeting’s topics, pietroalbini investigated whether it would
 be possible to redirect requests for Cargo 1.14.0 from the `rust-lang-ci` S3
 bucket to our CDN. The answer is no, as the S3 support for redirects requires a
 different endpoint than the one included in the manifest. The two main courses
-of action were to nothing (keeping the files in the `rust-lang-ci` S3 bucket),
+of action were to do nothing (keeping the files in the `rust-lang-ci` S3 bucket),
 or to rewrite and resign the manifest of Rust 1.14.0 to point to the CDN.
 
 Mark-Simulacrum was in favor of doing nothing, but pietroalbini pointed out
 keeping releases in two different places will make mirroring and caching
 efforts more complex, as mirror authors will have to special-case a separate
-domain just for a release. We then decided to rewrite and resing the manifest.
+domain just for a release. We then decided to rewrite and resign the manifest.
 
 shepmaster proposed to add a test somewhere to ensure this doesn’t happen
 again, but nobody on the team had the time to do this. If someone is interested