Pushing the docs to dev/ for branch: main, commit 5ca265989d1a12ded64d487128a6d26427f8f925

Author: dirty-cat-ci

dev/CHANGES.html

@@ -941,7 +941,7 @@ <h3>Highlights<a class="headerlink" href="#highlights" title="Link to this headi
 <section id="id15">
 <h3>New features<a class="headerlink" href="#id15" title="Link to this heading">#</a></h3>
 <ul class="simple">
-<li><p>The Skrub DataOps are new mechanism for building machine-learning
+<li><p>The skrub DataOps are new mechanism for building machine-learning
 pipelines that handle multiple tables and easily describing their
 hyperparameter spaces. Main PR: <a class="reference external" href="https://github.com/skrub-data/skrub/pull/1233">#1233</a> by <a class="reference external" href="https://github.com/jeromedockes">Jérôme Dockès</a>.
 Additional work from other contributors can be found

dev/CONTRIBUTING.html

@@ -772,7 +772,7 @@ <h2>Checking the quality of your code contribution<a class="headerlink" href="#c
 <section id="testing-the-code">
 <h3>Testing the code<a class="headerlink" href="#testing-the-code" title="Link to this heading">#</a></h3>
 <p>Tests for files in a given folder should be located in a sub-folder
-named <code class="docutils literal notranslate"><span class="pre">tests</span></code>: tests for Skrub objects are located in <code class="docutils literal notranslate"><span class="pre">skrub/tests/</span></code>,
+named <code class="docutils literal notranslate"><span class="pre">tests</span></code>: tests for skrub objects are located in <code class="docutils literal notranslate"><span class="pre">skrub/tests/</span></code>,
 tests for the dataframe API are in <code class="docutils literal notranslate"><span class="pre">skrub/_dataframe/tests/</span></code> and so on.</p>
 <p>Tests should check all functionalities of the code that you are going to
 add. If needed, additional tests should be added to verify that other

dev/_downloads/079702aaaa2e975f1668cb635070b620/0050_deduplication.zip

@@ -48,9 +48,9 @@
 transformers and models: this allows to save the learner, load it back later,
 and use it to make predictions on new data.
 
-This example is meant to be an introduction to Skrub DataOps, and as such it
+This example is meant to be an introduction to skrub DataOps, and as such it
 will not cover all the features. Further examples in the gallery
-:ref:`data_ops_examples_ref` go into more detail on Skrub DataOps
+:ref:`data_ops_examples_ref` go into more detail on skrub DataOps
 for more complex tasks.