We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 70cd2bb commit cbdf0dfCopy full SHA for cbdf0df
docs/devops-at-microsoft/progressive-experimentation-feature-flags.md
@@ -239,7 +239,7 @@ The feature teams own the decision as to whether they need a feature
239
flag or not for a given change. Not every change requires one, so if I
240
choose to change some element on a web page or whatever, it’s a judgment
241
call. But in the case of something like the revert feature I used as an
242
-example here, it was it was great to be able to have that behind a
+example here, it was great to be able to have that behind a
243
feature flag because that meant we could put the feature out in
244
production with controlled exposure. Teams own their feature area.
245
[Aaron Bjork talks about autonomy](https://youtu.be/-LvCJpnNljU), and
0 commit comments