From 8bd97afd2357483726949a34086f9fd8a6bf6f2d Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Tue, 18 May 2010 05:35:35 +0000 Subject: docs/ spelling fixes Just a few things in the documentation I noticed while reading up on OE. I don't understand why 'git diff' included "\ No newline at end of file" for some of these, or how I could instruct it not to, but I also didn't want to pick apart my patch outside of git. Signed-off-by: Michael Jones --- docs/usermanual/reference/class_image.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/usermanual/reference/class_image.xml') diff --git a/docs/usermanual/reference/class_image.xml b/docs/usermanual/reference/class_image.xml index b591e9aae2..227f7e1cd0 100644 --- a/docs/usermanual/reference/class_image.xml +++ b/docs/usermanual/reference/class_image.xml @@ -349,10 +349,10 @@ Alias /bogofeed ${DEPLOY_DIR} deploy/ipk). Now, every image built will automatically contain feed configs for the deploy directory (as of time of writing, deploy directory is internally structured with - per-arch subdirectories; so, there several feed configs are being generated, one for each subdirectory). + per-arch subdirectories; so, there are several feed configs being generated, one for each subdirectory). - \ No newline at end of file + -- cgit v1.2.3