From b8cb57fe6d24ecd2e95dbde3c338c3531cc77581 Mon Sep 17 00:00:00 2001 From: Vinay Datta Date: Tue, 24 Mar 2026 18:24:28 +0530 Subject: [6.0.x] Fixed #36999 -- Removed mention of Ruby on Rails from tutorial part 2. This comparison wasn't fleshed out, so it was distracting. Backport of f3bdfd2065373272ebb637785cea2313582a8b8c from main. --- docs/intro/tutorial02.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/intro/tutorial02.txt') diff --git a/docs/intro/tutorial02.txt b/docs/intro/tutorial02.txt index 8f99965a47..dc635ffed7 100644 --- a/docs/intro/tutorial02.txt +++ b/docs/intro/tutorial02.txt @@ -95,10 +95,9 @@ additional metadata. Django follows the :ref:`DRY Principle `. The goal is to define your data model in one place and automatically derive things from it. - This includes the migrations - unlike in Ruby On Rails, for example, - migrations are entirely derived from your models file, and are essentially a - history that Django can roll through to update your database schema to - match your current models. + This includes the migrations, which are derived from your models file. + They form a history that Django uses to update your database schema + to match your current models. In our poll app, we'll create two models: ``Question`` and ``Choice``. A ``Question`` has a question and a publication date. A ``Choice`` has two -- cgit v1.3