1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
Author: Andreas Tille <tille@debian.org>
Last-Update: Thu, 14 Jul 2016 10:16:38 +0200
Description: Start fixing some spelling issues
--- a/GO/Handlers/obj.pm
+++ b/GO/Handlers/obj.pm
@@ -60,7 +60,7 @@ as files are parsed, objects are created
datatype is being parsed, the classes of the created objects will be
different - eg GO::Model::Term, GO::Model::Association etc
-the way to access all of thses is through the top level graph object
+the way to access all of these is through the top level graph object
eg
--- a/GO/Model/Association.pm
+++ b/GO/Model/Association.pm
@@ -224,7 +224,7 @@ returns a score for the association base
This is an EXPERIMENTAL method; it may be removed in future versions.
-The evidence fields can be thought of in a loose hierachy:
+The evidence fields can be thought of in a loose hierarchy:
TAS
IDA
--- a/GO/Model/Evidence.pm
+++ b/GO/Model/Evidence.pm
@@ -77,7 +77,7 @@ used to set the GO::Model::Xref list fro
will actually add two GO::Model::Xref objects
-This method doesnt really belong in the GO::Model::* hierarchy as it
+This method doesn't really belong in the GO::Model::* hierarchy as it
contains parsing code. Its a minor hack mainly due to the fact that
this data is still denormalized in the database.
--- a/GO/Model/Graph.pm
+++ b/GO/Model/Graph.pm
@@ -93,7 +93,7 @@ Relationships can also be seen as arcs i
subject being equivalent to the child, and the object equivalent to
the parent. The arc is labeled with the predicate/relationship-type.
-perl doesnt handle bidirectional links between objects too well, so
+perl doesn't handle bidirectional links between objects too well, so
rather than having the relationship object know about the terms or the
term know about the realtionships, all the graph info is in the
Graph object
|
