From 055d38ae769399b13265dceec074c7f88661d8f7 Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Wed, 28 Sep 2022 19:35:29 +0200 Subject: Use curly apostrophe everywhere --- 2022/prepare.md | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) (limited to '2022/prepare.md') diff --git a/2022/prepare.md b/2022/prepare.md index fe069fd8..415238c4 100644 --- a/2022/prepare.md +++ b/2022/prepare.md @@ -17,10 +17,10 @@ updates. ### Guidelines for conduct Please review our [[guidelines for conduct|conduct]] when preparing -your talk, to make sure we're all on the same page and strive to make -the event a great experience for all. If you're not sure whether your +your talk, to make sure we’re all on the same page and strive to make +the event a great experience for all. If you’re not sure whether your talk or presentation style meets the guidelines laid out in the -guidelines for conduct, we'd be happy to help. You can email Sacha +guidelines for conduct, we’d be happy to help. You can email Sacha Chua at to chat more about this. ### Recording your talk @@ -36,7 +36,7 @@ more accessible and searchable. To make it easier for organizers and attendees to correctly pronounce your name, please start your video with something along the lines of: -"Hi! I'm ${NAME} and I'll be talking about ${TOPIC}." +"Hi! I’m ${NAME} and I’ll be talking about ${TOPIC}." Please **upload your prerecording(s) (and script/notes if any) via FTP** to the FTP server we have set up with the following details: @@ -61,7 +61,7 @@ $ ftp ftp-upload.emacsconf.org 21 > anonymous > passive > cd upload-here -> send /local/path/to/file.ext file.ext # Don't forget the 2nd arg! +> send /local/path/to/file.ext file.ext # Don’t forget the 2nd arg! # Ctrl-D to exit ``` @@ -95,7 +95,7 @@ your video recordings: - [Blender](//www.blender.org) - [Pitivi](http://www.pitivi.org) -Per GNU Project's +Per GNU Project’s [Guide to Formats](//audio-video.gnu.org/docs/formatguide.html), we prefer to receive prerecorded videos in formats unencumbered by software patents, such as `video/webm` (WebM-encoded video files, with @@ -136,7 +136,7 @@ information. We ask that speakers who plan to participate in live Q&A sessions schedule a short tech-check in the weeks leading to the conference; this is to ensure -that you can perform all the common tasks you'd need such as sharing your +that you can perform all the common tasks you’d need such as sharing your screen or toggling your microphone. We use BigBlueButton for our video-conferencing needs, and a quick way to @@ -144,15 +144,15 @@ familiarize yourself with it is to run it in a test-room: If this is your first time at EmacsConf or if you run into any problems, -please get in touch with us and we'll sort things out together! In those -cases, since we'll need to schedule a 1-on-1 tech-check with you, we ask that +please get in touch with us and we’ll sort things out together! In those +cases, since we’ll need to schedule a 1-on-1 tech-check with you, we ask that you email the closest volunteer to your timezone in the list below (or zaeph if none of the timezones is a good fit). You can also visit us at [#emacsconf-org on Libera](irc://libera.chat/#emacsconf-org). We will likely schedule those 1-on-1 tech-checks with you on Saturdays or Sundays, but we would be happy to try and work out another time if that -doesn't work for you. +doesn’t work for you. @@ -203,7 +203,7 @@ doesn't work for you.
-If you'd like to help out with the tech-checks, feel free to add your name and +If you’d like to help out with the tech-checks, feel free to add your name and email to the above list and email <zaeph@zaeph.net> to plan the logistics. @@ -213,7 +213,7 @@ Thank you so much for helping with EmacsConf 2022! ## Can I present live? -Tech issues kept happening during EmacsConf 2020, so we'd really +Tech issues kept happening during EmacsConf 2020, so we’d really prefer that all talks have prerecorded videos. There might be time for live questions and answers over a web conference, though, so if you can record a short video covering your main points, you might be @@ -226,7 +226,7 @@ could fit everything in at full length! (Maybe EmacsConf month?) Please think of your video as a short teaser that can get people interested and point them to where they can find out more. You can email links and other notes to add to the -wiki page for your talk. If you'd like to record a longer video *in +wiki page for your talk. If you’d like to record a longer video *in addition* to the short one for the main conference, please feel free to send us that too. @@ -242,12 +242,12 @@ broadcast, you may ask the host to field you a couple of questions to address extra points that couldn’t make the cut. We’ll have to be subtle about it, so mum’s the word! -## I can't figure out how to record the video. Can I just present the talk? +## I can’t figure out how to record the video. Can I just present the talk? We might be able to help you record your talk using the BigBlueButton web conferencing system before November 7. Please email with some times that might work for you and -we'll see if a volunteer can meet up with you to record it. +we’ll see if a volunteer can meet up with you to record it. ## How do I show my keystrokes on screen? @@ -257,16 +257,16 @@ In Emacs, you can use buffer. For a system-wide solution, you can look into [screenkey](https://gitlab.com/screenkey/screenkey). -## I'm not used to talking to myself. Can I present the talk to someone? +## I’m not used to talking to myself. Can I present the talk to someone? We might be able to help you record your talk using the BigBlueButton web conferencing system before November 7. Please email with some times that might work for you and -we'll see if a volunteer can meet up with you to record it. +we’ll see if a volunteer can meet up with you to record it. ## Can I see the other proposed talks? -Once we've emailed all the speakers about their acceptance, we'll put +Once we’ve emailed all the speakers about their acceptance, we’ll put up the talk wiki pages. That way, you can see what else is going on in the conference and maybe coordinate with other speakers in order to minimize overlap and maximize awesomeness. @@ -274,7 +274,7 @@ minimize overlap and maximize awesomeness. ## What if there are lots of great questions during Q&A and we run out of time? You can continue answering questions on the collaborative pad or IRC, -and we'll copy questions and answers onto the wiki page +and we’ll copy questions and answers onto the wiki page afterwards. You can also answer questions on the wiki page even after the event. An extended live demo or Q&A session might be possible if someone @@ -284,7 +284,7 @@ contact us at . ## More questions? -Please email . We'd love to hear from you. +Please email . We’d love to hear from you. Thanks for contributing to EmacsConf 2022! -- cgit v1.2.3