Fossil SCM
Markdownism fix in a Wiki-formatted doc
Commit
cbca374c37eb1a501dfc75e5595166339ddff1ddf2a3dafb54aece6128b05ce4
Parent
2686bad19a267fc…
1 file changed
+1
-1
+1
-1
| --- www/branching.wiki | ||
| +++ www/branching.wiki | ||
| @@ -148,11 +148,11 @@ | ||
| 148 | 148 | |
| 149 | 149 | <blockquote> |
| 150 | 150 | <b>Key Distinction:</b> A branch is a <i>named, intentional</i> fork. |
| 151 | 151 | </blockquote> |
| 152 | 152 | |
| 153 | -Forks *may* be intentional, but most of the time, they're accidental. | |
| 153 | +Forks <i>may</i> be intentional, but most of the time, they're accidental. | |
| 154 | 154 | |
| 155 | 155 | Figure 4 shows an example of a project where there are two branches, one |
| 156 | 156 | for development work and another for testing. |
| 157 | 157 | |
| 158 | 158 | <table border=1 cellpadding=10 hspace=10 vspace=10 align="center"> |
| 159 | 159 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -148,11 +148,11 @@ | |
| 148 | |
| 149 | <blockquote> |
| 150 | <b>Key Distinction:</b> A branch is a <i>named, intentional</i> fork. |
| 151 | </blockquote> |
| 152 | |
| 153 | Forks *may* be intentional, but most of the time, they're accidental. |
| 154 | |
| 155 | Figure 4 shows an example of a project where there are two branches, one |
| 156 | for development work and another for testing. |
| 157 | |
| 158 | <table border=1 cellpadding=10 hspace=10 vspace=10 align="center"> |
| 159 |
| --- www/branching.wiki | |
| +++ www/branching.wiki | |
| @@ -148,11 +148,11 @@ | |
| 148 | |
| 149 | <blockquote> |
| 150 | <b>Key Distinction:</b> A branch is a <i>named, intentional</i> fork. |
| 151 | </blockquote> |
| 152 | |
| 153 | Forks <i>may</i> be intentional, but most of the time, they're accidental. |
| 154 | |
| 155 | Figure 4 shows an example of a project where there are two branches, one |
| 156 | for development work and another for testing. |
| 157 | |
| 158 | <table border=1 cellpadding=10 hspace=10 vspace=10 align="center"> |
| 159 |