From ea56a5e7a802a46f9ad6fe12480e16dc587c09b2 Mon Sep 17 00:00:00 2001 From: Evan Martin Date: Sun, 12 Jul 2009 01:38:40 +0100 Subject: [PATCH] [docs] Fix typos and remove mentions of SVN Signed-off-by: Emmanuele Bassi --- HACKING | 3 ++- clutter/cogl/cogl-path.h | 2 +- tests/README | 2 +- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/HACKING b/HACKING index 74873505c..3b403db60 100644 --- a/HACKING +++ b/HACKING @@ -93,7 +93,8 @@ RELEASES In making a new release; - - Check out a fresh copy from SVN. + - Verify your working directory is fresh; i.e., check out a fresh copy + or "git reset --hard release_branch && git clean -f". - Verify versioning in configure.ac, increasing relevant clutter_major_version/clutter_minor_version/clutter_micro_version diff --git a/clutter/cogl/cogl-path.h b/clutter/cogl/cogl-path.h index be5a979e3..b6305391a 100644 --- a/clutter/cogl/cogl-path.h +++ b/clutter/cogl/cogl-path.h @@ -169,7 +169,7 @@ void cogl_path_rel_line_to (float x, * @center_x: X coordinate of the elliptical arc center * @center_y: Y coordinate of the elliptical arc center * @radius_x: X radius of the elliptical arc - * @radius_y: Y radious of the elliptical arc + * @radius_y: Y radius of the elliptical arc * @angle_1: Angle in the unit-circle at which the arc begin * @angle_2: Angle in the unit-circle at which the arc ends * diff --git a/tests/README b/tests/README index 5904884da..7aaf450e6 100644 --- a/tests/README +++ b/tests/README @@ -8,5 +8,5 @@ The micro-bench/ tests should be focused perfomance test, ideally testing a sing The interactive/ tests are any tests whos status can not be determined without a user looking at some visual output, or providing some manual input etc. This covers most of the original Clutter tests. Ideally some of these tests will be migrated into the conformance/ directory so they can be used in automated nightly tests. Other notes: -All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the aproach taken for testing. +All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the approach taken for testing.