@@ -14,9 +14,9 @@ Before submitting a bug:
14
14
* Double-check the official :doc: `documentation </index >` to see if you're not misusing the
15
15
framework;
16
16
17
- * Ask for assistance on `Stack Overflow `_ on the #symfony ` IRC channel`_, or on
18
- the #support channel of ` the Symfony Slack ` _ if you're not sure if your issue
19
- is really a bug.
17
+ * Ask for assistance on `Stack Overflow `_, on the #support channel of
18
+ ` the Symfony Slack `_, or on the #symfony ` IRC channel ` _ if you're not sure if
19
+ your issue is really a bug.
20
20
21
21
If your problem definitely looks like a bug, report it using the official bug
22
22
`tracker `_ and follow some basic rules:
@@ -33,11 +33,11 @@ If your problem definitely looks like a bug, report it using the official bug
33
33
* Give as much detail as possible about your environment (OS, PHP version,
34
34
Symfony version, enabled extensions, ...);
35
35
36
- * If you want to provide a stack trace you got on an html page, be sure to
36
+ * If you want to provide a stack trace you got on an HTML page, be sure to
37
37
provide the plain text version, which should appear at the bottom of the
38
38
page. *Do not * provide it as a screenshot, since search engines will not be
39
39
able to index the text inside them. Same goes for errors encountered in a
40
- terminal, do not take a screenshot, but learn how to copy/paste from it . If
40
+ terminal, do not take a screenshot, but copy/paste the contents . If
41
41
the stack trace is long, consider enclosing it in a `<details> html tag `_.
42
42
**Be wary that stack traces may contain sensitive information, and if it is
43
43
the case, be sure to redact them prior to posting your stack trace. **
0 commit comments