diff --git a/docs/technical-documentation/object_renaming_research_summary.md b/docs/technical-documentation/object_renaming_research_summary.md
index 1facdc8691..575770f1a0 100644
--- a/docs/technical-documentation/object_renaming_research_summary.md
+++ b/docs/technical-documentation/object_renaming_research_summary.md
@@ -27,7 +27,7 @@ In addition to improved documentation, the tests showed us that we need to impro
 
 **Description:** The issues with table columns ([\#420](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/420), [\#753](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/753), [\#2839](https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2839)) are something we had in mind for a very long time and finally had a chance to work on a solution that would improve them, and possibly some of the other resources. In short, the use case for table columns consists of two use cases connected to each other:
 
-- Ignoring the order of columns after creation. Users should be able to reorder, add, and remove columns from any place while still having somewhat control over column order on the Snowlake side.
+- Ignoring the order of columns after creation. Users should be able to reorder, add, and remove columns from any place while still having somewhat control over column order on the Snowflake side.
 - Updating a given column instead of removing and adding it again. Ignoring the order was an additional challenge because if someone wants to order the columns and change their name in one apply, then we need a way to identify this column to perform the correct action.
 
 **Tests:** The tests were carried out on a resource created only for the purpose of the research ([resource reference](https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/pkg/resources/object_renaming_lists_and_sets.go#L125)). Note that it won’t be normally visible and no other changes in other resources were made. We tested a few approaches regarding order ignoring and one on updating items.
diff --git a/pkg/architest/architest_test.go b/pkg/architest/architest_test.go
index 419f78c503..b53a0d031d 100644
--- a/pkg/architest/architest_test.go
+++ b/pkg/architest/architest_test.go
@@ -120,6 +120,7 @@ func Test_Files(t *testing.T) {
 		expectedMethodNames []string
 	}{
 		{filePath: "testdata/dir1/sample1.go", expectedMethodNames: []string{}},
+		// object methods are skipped
 		{filePath: "testdata/dir1/sample2.go", expectedMethodNames: []string{"A"}},
 	}
 	for _, tt := range tests1 {
diff --git a/pkg/architest/file.go b/pkg/architest/file.go
index a2d781a719..597402a868 100644
--- a/pkg/architest/file.go
+++ b/pkg/architest/file.go
@@ -42,7 +42,7 @@ func (f *File) ExportedMethods() Methods {
 	for _, d := range f.fileSrc.Decls {
 		if v, ok := d.(*ast.FuncDecl); ok {
 			name := v.Name.Name
-			if ast.IsExported(name) {
+			if ast.IsExported(name) && v.Recv == nil {
 				allExportedMethods = append(allExportedMethods, *NewMethod(name, f))
 			}
 		}
diff --git a/pkg/architest/testdata/dir1/sample2.go b/pkg/architest/testdata/dir1/sample2.go
index 7ba18f8743..ccbd1b7318 100644
--- a/pkg/architest/testdata/dir1/sample2.go
+++ b/pkg/architest/testdata/dir1/sample2.go
@@ -3,3 +3,9 @@ package dir1
 func A() {}
 
 func a() {}
+
+type obj struct{}
+
+func (o obj) Exported() {}
+
+func (o obj) private() {}