From owner-svn-doc-all@freebsd.org Sun Aug 12 09:18:27 2018 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB1B9106A354; Sun, 12 Aug 2018 09:18:26 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A10178040E; Sun, 12 Aug 2018 09:18:26 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7E5A02415B; Sun, 12 Aug 2018 09:18:26 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id w7C9IQxE043271; Sun, 12 Aug 2018 09:18:26 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id w7C9IQnC043270; Sun, 12 Aug 2018 09:18:26 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201808120918.w7C9IQnC043270@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Sun, 12 Aug 2018 09:18:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52117 - head/en_US.ISO8859-1/articles/problem-reports X-SVN-Group: doc-head X-SVN-Commit-Author: eadler X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/problem-reports X-SVN-Commit-Revision: 52117 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 09:18:27 -0000 Author: eadler Date: Sun Aug 12 09:18:26 2018 New Revision: 52117 URL: https://svnweb.freebsd.org/changeset/doc/52117 Log: problem-reports: formatting; pet igor Translators can ignore. Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/problem-reports/article.xml Sun Aug 12 09:11:17 2018 (r52116) +++ head/en_US.ISO8859-1/articles/problem-reports/article.xml Sun Aug 12 09:18:26 2018 (r52117) @@ -198,7 +198,7 @@ versions. If the problem is in a port, consider filing a bug with the - upstream. The &os; Project can not fix all bugs in all + upstream. The &os; Project can not fix all bugs in all software. @@ -250,9 +250,9 @@ Next, the searchable &os; - PR database (Bugzilla). Unless the problem is recent - or obscure, there is a fair chance it has already been - reported. + PR database (Bugzilla). Unless the problem is + recent or obscure, there is a fair chance it has already + been reported. @@ -529,7 +529,8 @@ Before Beginning Similar considerations apply to use of the - web-based + web-based PR submission form. Be careful of cut-and-paste operations that might change whitespace or other text formatting. @@ -805,9 +806,9 @@ Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect - assumptions about the problem. It should include the - actions you need to take to reproduce the problem. If you - know any workaround, include it. It not only helps other + assumptions about the problem. It should include the + actions you need to take to reproduce the problem. If you + know any workaround, include it. It not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem. @@ -834,10 +835,10 @@ initial report, please submit a follow up. The number one reason for a bug not getting fixed is lack of communication with the originator. The easiest way is to use the comment - option on the individual PR's web page, which you can reach - from the PR - search page. + option on the individual PR's web page, which you can reach + from the PR + search page. If the problem report remains open after the problem has gone away, just add a comment