diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2007-09-10 03:46:06 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2007-09-10 03:46:06 +0000 |
| commit | 49e4e4f9ce1ed5198385353ab5a88693f9ab17c3 (patch) | |
| tree | 4120007925c3793130813eb26ec714ef696104eb | |
| parent | b82a44d2706a08ddf848960f8b777f47db66f376 (diff) | |
Attempted to bold part of docs/contributing.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@6084 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/contributing.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/contributing.txt b/docs/contributing.txt index 4de31acc63..f8c8499995 100644 --- a/docs/contributing.txt +++ b/docs/contributing.txt @@ -444,12 +444,12 @@ any documentation of *new* features will be seen by Django users who don't necessarily have access to those features yet, because they're only using the latest release. Thus, our policy is: - All documentation of new features should be written in a way that clearly + **All documentation of new features should be written in a way that clearly designates the features are only available in the Django development - version. + version.** - Assume documentation readers are using the latest release, not the - development version. + **Assume documentation readers are using the latest release, not the + development version.** Our traditional way of marking new features is by prefacing the features' documentation with: "New in Django development version." Changes aren't |