Some typo corrections

content/interviews/dusseault-interoperability.md

@@ -59,7 +59,7 @@ One of the interesting things with the FTC stuff at Microsoft and with the stand
 
 There's a Mark Twain quote about how a man's opinions are remarkably formed by what is to his benefit. That was absolutely true for the bulk of Microsoft employees. There are very few Machiavellian people that I ever worked with inside Microsoft, but if a Machiavellian purpose was needed to adopt an open standard, sometimes somebody would say, "I think we should adopt this open standard for instant messaging, and an open standard would be great for the world and the internet and users." But you had to justify it to VPs. Because at Microsoft internally, the management had a reputation for being cutthroat, I think people would sometimes pitch their stuff in a Machiavellian way, even if what they really wanted was for the whole internet to interoperate, and they wanted to be part of it.
 
-*Let's turn to the WebDAV process. Talk about what was going on with Exchange and why standards became part of the development of this core piece of the Microsoft Office product offering.* TKTK
+*Let's turn to the WebDAV process. Talk about what was going on with Exchange and why standards became part of the development of this core piece of the Microsoft Office product offering.*
 
 I was recruited to the Exchange team internally at Microsoft because it was doing amazing things. The vision, the architectural vision---Alex Hoffman was one of the people holding this vision, Joel Soderberg was another. Several people were on board with this vision of having a standardized access protocol to the massive amounts of data in an enterprise email, calendaring, task, and notes server.
 
@@ -87,7 +87,7 @@ But also, once you have a collection and an extensible set of properties, the ve
 
 It's turned into a little-known but still widespread document sharing and collaboration basis. There are research organizations around the world and universities that agree to use WebDAV-based shares so that they can each access each other's research datasets, research papers in progress and other materials, presentations, and things that they're working on across these boundaries and with their different tools. File sharing, file sync, network file access, that kind of thing is definitely ongoing.
 
-As I know you know, calendaring---we built calendaring on top of WebDAV. When WebDAV is used to access a calendar, you can do that with multiple different clients against multiple different implementation servers, thanks to CalDAV. I think CardDAV (similar concept but for address books) has some uptake and interoperability as well.
+As I know you know, calendaring---we built calendaring on top of WebDAV. When WebDAV is used to access a calendar, you can do that with multiple different clients against multiple different implementation servers, thanks to CalDAV. I think CardDAV---similar concept but for address books---has some uptake and interoperability as well.
 
 *I use all three of them constantly in my life, mainly because I live on several Nextcloud servers. Can we zero in on the calendaring piece? You mentioned earlier that at this time calendars across different services were not necessarily interoperable. Can you say about the ecosystem as you found it and how standardization started to change it?*
 
@@ -155,7 +155,7 @@ I think people, when they are worried about something bad, are more afraid of so
 
 *I'm curious if you could reflect on how that standards process has shaped the way you use these technologies today. Do you see them differently than you think other people might who were not part of the processes of working on these standards? Do you notice things that you think maybe most people don't notice because of these experiences?*
 
-Probably, but I'm also very pragmatic. You said you use a bunch of Nextcloud services, which I love. I just do what most people do, and I use Gmail for mail and Apple Photos for photos. It's a very pragmatic, or you could call it lazy, decision. Then I whine about them, and I could see how they could be so much better because of the dreams we had.
+Probably, but I'm also very pragmatic. You said you use a bunch of Nextcloud services, which I love. I just do what most people do, and I use Gmail for mail and Apple Photos for photos. It's a very pragmatic---or you could call it lazy---decision. Then I whine about them, and I could see how they could be so much better because of the dreams we had.
 
 *I recall reading in an earlier interview you gave that you took a hiatus from standards, that you had enough and you stepped back. Can you say about that experience?*
 
@@ -167,7 +167,7 @@ I had young kids. It was getting harder and harder to travel. You can travel wit
 
 I was getting sick of the ten-year time horizon in standards. Everything I worked on, would I have to wait ten or twelve years to show my mom, who's a great supporter of me and my work?
 
-Chartering a working group---I was an area director, so I was even farther removed from anything practical or immediate. I was recruiting people to come to the IETF, I was helping them charter working groups, I was choosing chairs, I was helping them write a charter so that then the chairs could choose the editors to write the drafts to meet the charter to then be approved by the working group to then be sent to the IETF to then become RFCs, and then implementers really start thinking about them. You can see why this becomes a ten-year time horizon before it ends up in something mass market.
+I was an area director, so I was even farther removed from anything practical or immediate. I was recruiting people to come to the IETF, I was helping them charter working groups, I was choosing chairs, I was helping them write a charter so that then the chairs could choose the editors to write the drafts to meet the charter to then be approved by the working group to then be sent to the IETF to then become RFCs, and then implementers really start thinking about them. You can see why this becomes a ten-year time horizon before it ends up in something mass market.
 
 *How does that experience make you reflect on the openness of the IETF? In some respects, it's an incredibly open organization and process, in the sense that discussions are on email lists and there isn't a closed membership logic that some standards bodies have. But at the same time, there are these bureaucracy of its own and the kinds of social norms and so forth that some have found off-putting. How do you end up understanding the idea of openness in that organization?*
 
@@ -177,11 +177,11 @@ One of the things that I think saves the IETF in its extreme openness---because
 
 Many of them look at it and say it's impossible, it's impossible to be that open, it's impossible to do that well. Kaliya has dug into the history of how Tim Berners-Lee came to the IETF, saw utter chaos because the IETF was in the middle of a transition, and said, this is crazy, this is impossible to make any progress in this environment, and went off and founded the W3C with a closed membership model so that you can make progress. But then the IETF recovered from its existential overturn and continued to make progress, although slowly.
 
-I think what saves the IETF is, when it works on very technical things, the technical things themselves are somewhat of a barrier to entry. Then there are cultural norms around, did you read the documents before you start commenting on them, which help. We're not just asking for opinion on policy or ideas or vision statements. We're asking for---we're opening up to public opinion on technical specifications. Did you read the forty pages before you comment? That makes open participation a lot more manageable.
+I think what saves the IETF is, when it works on very technical things, the technical things themselves are somewhat of a barrier to entry. Then there are cultural norms around, did you read the documents before you start commenting on them, which help. We're not just asking for opinion on policy or ideas or vision statements. We're opening up to public opinion on technical specifications. Did you read the forty pages before you comment? That makes open participation a lot more manageable.
 
 I'm part of a process right now in which the IETF is advancing its participation models to have more effective moderation. When the open participation allows harmful participation, there's a lot of concern about silencing when you talk about moderation in these forums. But there's a whole suite of voices, there's a whole population of voices that are silenced because they are turned off so early. They may even be invited, come to an IETF, IETF has outreach, but then they try to participate and they're treated badly, like I was at first, and leave. You never get that voice.
 
-There are---I've talked to many people individually who feel that they'd like to participate in the IETF, but it's just not worth the stress, the emotional stress, the aggravation.
+I've talked to many people individually who feel that they'd like to participate in the IETF, but it's just not worth the stress, the emotional stress, the aggravation.
 
 *What kinds of things are you working on to address that issue?*
 
@@ -201,11 +201,11 @@ When I said I joined Microsoft as a program manager right out of university, tha
 
 I came back to standards with even more confidence about my technical abilities. I always knew I was capable of understanding, but more confidence in my opinions. It's harder to convince me that an idea that I don't like---something in my now well-trained gut is giving me a little bit---experience really builds pattern recognition, and the pattern recognition I was starting to trust and say, I see what they're saying, but something's niggling, and I have to work with this problem. If I have time, I'll work with the problem to analyze what's making me feel a little bit off about it. That confidence.
 
-But also, some of the amazing people I worked with---my cofounder at that last startup is just a terrific individual. She taught me so much about being a manager, being a leader, listening to people. I've come back simultaneously very confident in my management and leadership skills compared to my hubris, my less-founded confidence of a younger me. But now I also have a confidence in my technical skills, which the younger me didn't have to the same extent. I no longer have imposter syndrome, whether it was imposter syndrome in the beginning.
+But also, the amazing people I worked with---my cofounder at that last startup is just a terrific individual. She taught me so much about being a manager, being a leader, listening to people. I've come back simultaneously very confident in my management and leadership skills compared to my hubris, my less-founded confidence of a younger me. But now I also have a confidence in my technical skills, which the younger me didn't have to the same extent. I no longer have imposter syndrome, whether it was imposter syndrome in the beginning.
 
 I remember being very defensive about my technical skills back then. After a year of working together with an IETF colleague, he said, Lisa, let's talk to each other about how we're doing and give each other feedback. I said okay.
 
-One of his bits of feedback was, I feel sometimes you don't know as much about a technical subject as you should because there are things you should know, and yet you're asking questions about it. I said -- have you heard about the Socratic method? His mind was blown.
+One of his bits of feedback was, I feel sometimes you don't know as much about a technical subject as you should because there are things you should know, and yet you're asking questions about it. I said, "Have you heard about the Socratic method?" His mind was blown.
 
 But I was also defensive about it. From my first year at Microsoft as an intern, can you get things done as an intern by walking into offices and telling people what to do? No. Can you ask questions until you either understand or have convinced them to change their mind? Yes. Nobody expects the twenty-five-year-old who looks twenty to have all the answers, so people have such patience for asking questions. I honed that skill at Microsoft and brought it to the IETF. I will continue asking questions for as long as I can until we get something better than what was making me start to ask questions.
 
@@ -215,7 +215,7 @@ But I was definitely defensive about it, and I felt I had to do things to prove
 
 *I think it's interesting that you've moved more toward the technical side as your career has progressed. It seems to me it's more common in the industry for people to begin with a high level of technical emphasis, as engineers building with particular new technologies, and then over time they grow into management and they become less in touch with the most current frameworks or whatever people are using right now. Do you feel like you've gone in some ways in an opposite direction from people around you?*
 
-I mentor people pretty regularly, and I'm often asking women who I mentor, do you want to get management tracked? Because if you get management tracked too early, your opportunities cap out. If you stay in the individual contributor, technical contributor for longer, somehow manage to combine that with a management role, then you're planning for five years in the future being a CTO, being the VP of engineering, instead of being the director of the project management team or something like that. Where do you want to end up? As a woman, how do you protect your---how do people see you so that you can get there?
+I mentor people pretty regularly, and I'm often asking women who I mentor, do you want to get management tracked? Because if you get management tracked too early, your opportunities cap out. If you stay in the individual contributor, technical contributor for longer, somehow manage to combine that with a management role, then you're planning for five years in the future being a CTO, being the VP of engineering, instead of being the director of the project management team or something like that. Where do you want to end up? As a woman, how do people see you so that you can get there?
 
 *Can you say about the contributions you're making now and the standards that you've been focusing on?*
 
@@ -237,9 +237,9 @@ One of the things I realized is there's purely selection bias. New people are th
 
 *I wonder if that direction that you've moved from more organizational work to more technical work could insulate you from some of those dynamics you observed.*
 
-I hope so. I also---I'm going to psychoanalyze people a little bit and say that I think---this is one thing that my last cofounder really helped me to see. She's amazing. She helped me to see people's trauma expressed in how they work. Sounds fluffy, but it's actually extremely specific.
+I hope so. I'm going to psychoanalyze people a little bit---this is one thing that my last cofounder really helped me to see. She's amazing. She helped me to see people's trauma expressed in how they work. Sounds fluffy, but it's actually extremely specific.
 
-I think we all know it by the time we're in our late twenties. We've all seen that friend who got badly hurt in a breakup or something, and they say I'm never going to date X again or make some statement about how they can't handle that risk, they can't take the risk of putting their hopes and love into that kind of situation ever again.
+I think we all know it by the time we're in our late twenties. We've all seen that friend who got badly hurt in a breakup or something, and they say I'm never going to date *x* again or make some statement about how they can't handle that risk, they can't take the risk of putting their hopes and love into that kind of situation ever again.
 
 I've also met founders who had a terrible cofounder experience and will say I can never found a company again, it's just terrible, it's a terrible experience, it hurts so much. Or people who take venture capital from the large number of, frankly, toxic investors and say I can never do that again, I've been---it hurt too much.
 

content/interviews/mayer-mediation.md

@@ -166,7 +166,7 @@ I basically looked at them and said, "All right, here's what I think is going on
 
 *You helped them develop a shared meta-story about what was going on between them.*
 
-That's exactly it. And it worked. I'm sure to this day it still is a striggpe, because I think it's a long-term relationship--- and they're probably completely different players, but the structure is still there. They probably still struggle with that.
+That's exactly it. And it worked. I'm sure to this day it still is a struggle, because I think it's a long-term relationship---and they're probably completely different players, but the structure is still there. They probably still struggle with that.
 
 *Have you had experiences where ideas or practices that you've developed have been used in a way that you were not comfortable with?*